Files for my Home Assistent setup
iammexx / home-assistant-config Goto Github PK
View Code? Open in Web Editor NEWFiles for my Home Assistant setup
Files for my Home Assistant setup
My 5 day forecast card is showing Thursday through to Monday. Unfortunately, the temperatures are displayed under the wrong days. At the time of posting this, today is Wednesday in Australia but today's weather is actually shown under THURSDAY and so on for the next 4 days.
In the screen shot I have shared, 7/19°C is actually today's temperature (Wednesday) and 11/20°C should be under Thursday, not Friday. The state of my sensor, sensor.wupws_temp_high_1d is showing 7/19°C so I know I have them matched to the correct entities in ui-lovelace.yaml
Following is an extract from my lovelace card. My sensors are all correct when I check their states so there must be a bug in the code of the dark-sky-weather-card.js file, possibly under the getDate function.
entity_forecast_high_temp_1: sensor.wupws_temp_high_1d entity_forecast_high_temp_2: sensor.wupws_temp_high_2d entity_forecast_high_temp_3: sensor.wupws_temp_high_3d entity_forecast_high_temp_4: sensor.wupws_temp_high_4d entity_forecast_high_temp_5: sensor.wupws_temp_high_5d
Can someone help?
When using, for example:
slot_l3: remove
slot_r3: remove
All sensors such as a time sensor, or binary door sensors, etc... stop updating. A refresh of the browser gets the new sensor values. After a refresh, the sensors stop working roughly 30 seconds later each time. If I comment out the slot_l3 and slot_r3 in the settings, everything works as it should.
I should also say, that using the above config, the slot 3 is removed as it should be on the card; however all sensors stop updating within 30 seconds. I have rebooted the hassio appliance multiple times, using multiple browsers on different computes, deleted caches, rolled HA back to older versions, etc... and only when I comment out those 2 lines do the sensors continue to update after 30 seconds.
type: 'custom:dark-sky-weather-card'
entity_current_conditions: sensor.dark_sky_icon
entity_temperature: sensor.dark_sky_temperature
entity_forecast_high_temp_1: sensor.dark_sky_daytime_high_temperature_1
entity_forecast_high_temp_2: sensor.dark_sky_daytime_high_temperature_2
entity_forecast_high_temp_3: sensor.dark_sky_daytime_high_temperature_3
entity_forecast_high_temp_4: sensor.dark_sky_daytime_high_temperature_4
entity_forecast_high_temp_5: sensor.dark_sky_daytime_high_temperature_5
entity_forecast_icon_1: sensor.dark_sky_icon_1
entity_forecast_icon_2: sensor.dark_sky_icon_2
entity_forecast_icon_3: sensor.dark_sky_icon_3
entity_forecast_icon_4: sensor.dark_sky_icon_4
entity_forecast_icon_5: sensor.dark_sky_icon_5
entity_forecast_low_temp_1: sensor.dark_sky_overnight_low_temperature_0
entity_forecast_low_temp_2: sensor.dark_sky_overnight_low_temperature_1
entity_forecast_low_temp_3: sensor.dark_sky_overnight_low_temperature_2
entity_forecast_low_temp_4: sensor.dark_sky_overnight_low_temperature_3
entity_forecast_low_temp_5: sensor.dark_sky_overnight_low_temperature_4
entity_summary_1: sensor.dark_sky_summary_1
entity_summary_2: sensor.dark_sky_summary_2
entity_summary_3: sensor.dark_sky_summary_3
entity_summary_4: sensor.dark_sky_summary_4
entity_summary_5: sensor.dark_sky_summary_5
entity_sun: sun.sun
entity_visibility: sensor.dark_sky_visibility
entity_daytime_high: sensor.dark_sky_daytime_high_temperature_0
entity_wind_bearing: sensor.dark_sky_wind_bearing
entity_wind_speed: sensor.dark_sky_wind_speed
entity_humidity: sensor.dark_sky_humidity
entity_pressure: sensor.dark_sky_pressure
entity_apparent_temp: sensor.dark_sky_apparent_temperature
entity_daily_summary: sensor.dark_sky_daily_summary
entity_pop: sensor.dark_sky_precip_probability
entity_pop_intensity: sensor.dark_sky_precip_intensity
entity_pop_1: sensor.dark_sky_precip_probability_1
entity_pop_2: sensor.dark_sky_precip_probability_2
entity_pop_3: sensor.dark_sky_precip_probability_3
entity_pop_4: sensor.dark_sky_precip_probability_4
entity_pop_5: sensor.dark_sky_precip_probability_5
locale: en
static_icons: false
tooltip_bg_color: 'rgb( 75,155,239)'
tooltip_border_color: orange
tooltip_border_width: 3
tooltip_caret_size: 10
tooltip_fg_color: '#fff'
tooltip_left_offset: -12
tooltip_width: 100
tooltips: true
old_daily_format: false
time_format: 12
show_beaufort: true
slot_l3: remove
slot_r3: remove
Sunrise and sunset shown are being obtained from the HA location not the latitude / longitude specified.
This just started happening to me without me changing anything. It appears that there are issues with the CDN Lit uses (see: https://github.com/kalkih/mini-media-player/pull/58/files).
I tried replacing the import with the 4 lines from that PR but it didn't fix it for me, I end up with an empty card.
Hi,
I posted on your home assistant forum thread. However, I will also add it here:
First of all, I noticed that “Feels like” and “Today’s high” did not translate to Danish. I asked on the home assistant discord server, and got help figuring it out, including the next things I found.
I changed the fr case to:
case “da” :
return {
feelsLike: “Føles som”,
maxToday: “Højeste i dag”,
And it worked. Then I found that wind directions also did not translate, and were only written as acronyms, where I would prefer written out. So I changed it to:
const windDirections_da = [‘Nord’,‘Nord-Nordøst’,‘Nordøst’,‘Øst-Nordøst’,‘Øst’,‘Øst-Sydøst’,‘Sydøst’,‘Syd-Sydøst’,‘Syd’,‘Syd-Sydvest’,‘Sydvest’,‘Vest-Sydvest’,‘Vest’,‘Vest-Nordvest’,‘Nordvest’,‘Nord-Nordvest’,‘Nord’];
Then I noticed my wind speed was reporting km/h, where it should report km/t (hours = timer in danish). But adding it this, it was also giving me the m/s value and putting km/h unit on it. Lastly, I think the way of reporting the wind speed and direction was unnatural, so I changed it to report like “speed” from “direction”. I found out that changing the wind variable could do it:
var wind = this.config.entity_wind_speed && this.config.entity_wind_bearing ? html
Can you maybe include these things? :)
Hi,
I get this error in Lovelace:
Uncaught TypeError: Cannot read property 'unit_system' of undefined
07:34 components/system_log/init.py (ERROR)
I think my units are not defined properly
Hello
Could you make a tracker.json file so that we thru "custom updater" can update automaticly when new version is made!?
Thanks in advance!
Hi, could you create a fork of this beautifulll cart to works with pirate-weather?
Thanks a lot
Currently, the summary gives the total snowfall (and rain, presumably) for the week but it does not show daily expected snowfall. It would be great to add the daily expected accumulation (sensor.dark_sky_precip_accumulation) under each day similar to how the chance of precip is listed.
Hello,
i'm trying to add card to the my HA and have multiple errors.
Uncaught (in promise) TypeError: Cannot read property 'state' of undefined
at HTMLElement.get current [as current] (dark-sky-weather-card.js?v=7.1:307)
at HTMLElement.render (dark-sky-weather-card.js?v=7.1:33)
at HTMLElement.value (app-badd6e6f.js:2)
at HTMLElement.value (app-badd6e6f.js:2)
at HTMLElement.<anonymous> (app-badd6e6f.js:2)
at j (compatibility-e3292283.js:1)
at Generator._invoke (compatibility-e3292283.js:1)
at Generator.t.(anonymous function) [as next] (http://192.168.1.178:8123/frontend_es5/compatibility-e3292283.js:1:8262)
at k (app-badd6e6f.js:2)
at a (app-badd6e6f.js:2)
could you please correct me/my configuration related to dark-sky-weather-card
Thank you in advance,
My config:
resources:
- url: /local/custom_ui/dark-sky-weather-card.js?v=7.1
type: module
title: Home
views:
- badges:
- person.andrii_petrenko
- sensor.yr_symbol
- sun.sun
- sensor.ds_home_hourly_summary
- zone.home
cards:
- entities:
- entity: sensor.date_time
- entity: sensor.date_time_iso
- entity: sensor.time_utc
show_header_toggle: false
title: Information
type: entities
- entity: weather.home
name: Home
type: weather-forecast
- entity: weather.work
name: Work
type: weather-forecast
- type: 'custom:dark-sky-weather-card'
entity_current_conditions: sensor.dark_sky_icon
entity_temperature: sensor.dark_sky_temperature
entity_forecast_high_temp_1: sensor.dark_sky_daytime_high_temperature_1d
entity_forecast_high_temp_2: sensor.dark_sky_daytime_high_temperature_2d
entity_forecast_high_temp_3: sensor.dark_sky_daytime_high_temperature_3d
entity_forecast_high_temp_4: sensor.dark_sky_daytime_high_temperature_4d
entity_forecast_high_temp_5: sensor.dark_sky_daytime_high_temperature_5d
entity_forecast_icon_1: sensor.dark_sky_icon_1d
entity_forecast_icon_2: sensor.dark_sky_icon_2d
entity_forecast_icon_3: sensor.dark_sky_icon_3d
entity_forecast_icon_4: sensor.dark_sky_icon_4d
entity_forecast_icon_5: sensor.dark_sky_icon_5d
entity_forecast_low_temp_1: sensor.dark_sky_overnight_low_temperature_0d
entity_forecast_low_temp_2: sensor.dark_sky_overnight_low_temperature_1d
entity_forecast_low_temp_3: sensor.dark_sky_overnight_low_temperature_2d
entity_forecast_low_temp_4: sensor.dark_sky_overnight_low_temperature_3d
entity_forecast_low_temp_5: sensor.dark_sky_overnight_low_temperature_4d
entity_summary_1: sensor.dark_sky_summary_1d
entity_summary_2: sensor.dark_sky_summary_2d
entity_summary_3: sensor.dark_sky_summary_3d
entity_summary_4: sensor.dark_sky_summary_4d
entity_summary_5: sensor.dark_sky_summary_5d
panel: false
path: default_view
title: General
- badges: []
cards:
- aspect_ratio: 90%
type: iframe
url: >-
https://embed.windy.com/embed2.html?lat=37.899953&lon=-122.052297&zoom=9&level=surface&overlay=rain&menu=&message=&marker=&calendar=&pressure=&type=map&location=coordinates&detail=&detailLat=37.899953&detailLon=122.052297&metricWind=default&metricTemp=default&radarRange=-1
- type: horizontal-stack
panel: false
theme: default
title: Weather
Awesome card. Works great and keeps getting better.
Just wondering if there were any plans in the works to add an hourly forecast to the card now that the data is available? I don't want to bother putting something together myself (in lovelace) if you're going to be adding it to the card.
Hi, do you feel like making this card HACS compatible? HACS is the new plugin manager for home assistant. Lots of developers has added support.
When using this Dark-Sky-Weather-Card with Chrome, i see a huge increase on CPU load when the page is selected where this card is on. Also Firefox has a CPU increase, but not as much as chrome.
Idle CPU:
5062 xxxxx 20 0 831120 174304 112036 S 3.0 1.1 2:23.63 chrome
5113 xxxxx 20 0 533600 84092 58864 S 2.7 0.5 0:22.58 chrome
9211 xxxxx 20 0 588364 35456 26084 S 2.3 0.2 0:01.46 gnome-terminal-
8583 xxxxx 20 0 1078676 275896 116888 S 1.7 1.7 2:46.29 chrome
5327 xxxxx 20 0 763896 109040 66592 S 1.0 0.7 0:25.53 chrome
Card selected CPU:
8583 xxxxx 20 0 1082516 279148 117908 S 120.2 1.7 3:02.12 chrome
5108 xxxxx 20 0 573880 123952 85128 S 35.1 0.8 2:03.04 chrome
1812 root 20 0 661576 131140 106756 S 13.2 0.8 2:20.89 Xorg
5062 xxxxx 20 0 822924 174328 112020 S 5.0 1.1 2:25.40 chrome
5113 xxxxx 20 0 533600 84092 58864 S 3.3 0.5 0:23.82 chrome
5327 xxxxx 20 0 763896 109812 66592 S 1.3 0.7 0:25.96 chrome
Is this normal?
Edit: The increase is on the browser site
By default the card shows the forecast of the next 5 days - beginning with tomorrow.
I would like to begin with today. While I can already set the correct values if I begin with the “_0” values instead of “_1” in the config, the day names don’t reflect this.They start with FR (Friday) instead of today (Thursday).
IMO this is more elegant and space-saving than adding the same info above the forecast row. And predictions for more than 3 days in the future are inaccurate anyway.
Solution idea: allow config of a forecast start day (e.g. 0, 1, 2) and possible number of days so that the forecast shows e.g. today + 3 days or tomorrow + 4 days.
If you want to refactor a bit, you could think about removing the almost duplicate references to entity ids (.._0, .._1,...) and just have the user configure the prefix.
See here for the original forum post: https://community.home-assistant.io/t/custom-dark-sky-animated-weather-card/59816/1002
as of updating to HA 116, this card blocks the entire view from displaying, and a simple comment before the card in the config makes the view re-appear again.
which is an easy test, since I have it in an include (for years.....) like this:
- !include /config/lovelace/includes/include_darksky_weather_card.yaml
please have a look what could be causing this? I dont have any errors in the inspector unfortunately, so no hint or clue where to start.
Hello - Just got it working but it took quite a bit of fiddling. This was my first custom card (or any card), so I was learning from the README. That being said, I needed to do something other than what it said and my ui-lovelace.yaml file needed to look like this:
resources:
- url: /local/custom_ui/dark-sky-weather-card.js?v=7.1
type: module
title: Home Assistant
views:
- id: weather
title: Weather
cards:
- type: 'custom:dark-sky-weather-card'
entity_current_conditions: sensor.dark_sky_icon
entity_temperature: sensor.dark_sky_temperature
entity_forecast_high_temp_1: sensor.dark_sky_daytime_high_temperature_1
entity_forecast_high_temp_2: sensor.dark_sky_daytime_high_temperature_2
entity_forecast_high_temp_3: sensor.dark_sky_daytime_high_temperature_3
entity_forecast_high_temp_4: sensor.dark_sky_daytime_high_temperature_4
entity_forecast_high_temp_5: sensor.dark_sky_daytime_high_temperature_5
entity_forecast_icon_1: sensor.dark_sky_icon_1
entity_forecast_icon_2: sensor.dark_sky_icon_2
entity_forecast_icon_3: sensor.dark_sky_icon_3
entity_forecast_icon_4: sensor.dark_sky_icon_4
entity_forecast_icon_5: sensor.dark_sky_icon_5
entity_forecast_low_temp_1: sensor.dark_sky_overnight_low_temperature_0
entity_forecast_low_temp_2: sensor.dark_sky_overnight_low_temperature_1
entity_forecast_low_temp_3: sensor.dark_sky_overnight_low_temperature_2
entity_forecast_low_temp_4: sensor.dark_sky_overnight_low_temperature_3
entity_forecast_low_temp_5: sensor.dark_sky_overnight_low_temperature_4
entity_summary_1: sensor.dark_sky_summary_1
entity_summary_2: sensor.dark_sky_summary_2
entity_summary_3: sensor.dark_sky_summary_3
entity_summary_4: sensor.dark_sky_summary_4
entity_summary_5: sensor.dark_sky_summary_5
title
, views
, id
tags.Since Home Assistant V0.91.0 has just changed some sensors name, card configuration has to be changed for every sensor ending with a numerical value.
ie.
entity_forecast_high_temp_1: sensor.dark_sky_daytime_high_temperature_1
renamed to
entity_forecast_high_temp_1: sensor.dark_sky_daytime_high_temperature_1d
Thank you for your great component. Please consider structuring to work with hacs downloader/updater.
Hi there,
I am not really sure someone is gonna pick this up, considering the amount of open issue I don't feel like this card is being mantained anymore.
I think I found a conflict with the Button Entity Card, I did open an Issue on their github repository but it looks more something related to the DarkSky Weather Card, therefore... here I am :)
(Issue opened there: custom-cards/button-entity-row#9)
Long story short, the darksky-weather-card stop working with this error:
Uncaught SyntaxError: Identifier 'LitElement' has already been declared
at dark-sky-weather-card.js:1
This is happening only when i load (not use, simply load the resource in the configuration) the button-entity-row card
I am not a developer so I am not really capable of debug it more myself, but I am available if you need further informations (if that is something you need fix on your end).
Thanks
Andrea
I’ve been using this card and I like it a lot! Have one problem though - the card seems to be too wide when displayed on iPhone (XR), attached is a screenshot from Safari, in homeassitant companion app the gap from the right is not that big, but it’s there. I was trying to fix it myself, but have no clue. Can anyone help please?
Hello there,
I'm trying to configure this awesome looking card however i'm facing an issue :(
Here is what i get in the console:
dark-sky-weather-card.js?v=7.1:61 Uncaught (in promise) TypeError: Cannot read property 'state' of undefined
at dark-sky-weather-card.js?v=7.1:61
at Array.map ()
at HTMLElement.render (dark-sky-weather-card.js?v=7.1:55)
at HTMLElement.update (app.7bd99ba1.js:formatted:1367)
at HTMLElement.performUpdate (app.7bd99ba1.js:formatted:1188)
at HTMLElement._enqueueUpdate (app.7bd99ba1.js:formatted:1167)
I tried to figure out what was the issue but could not fix it I followed the installation instructions from the readme (except that i installed under custom-lovelace and not custom_ui, as i already have custom components there)
The sensors entities are correctly defined and report good values and i put the same lovelace configuration (required parametrs) as defined in the README
- type: 'custom:dark-sky-weather-card'
entity_current_conditions: sensor.dark_sky_icon
entity_temperature: sensor.dark_sky_temperature
entity_forecast_high_temp_1: sensor.dark_sky_daytime_high_temperature_1d
entity_forecast_high_temp_2: sensor.dark_sky_daytime_high_temperature_2d
entity_forecast_high_temp_3: sensor.dark_sky_daytime_high_temperature_3d
entity_forecast_high_temp_4: sensor.dark_sky_daytime_high_temperature_4d
entity_forecast_high_temp_5: sensor.dark_sky_daytime_high_temperature_5d
entity_forecast_icon_1: sensor.dark_sky_icon_1d
entity_forecast_icon_2: sensor.dark_sky_icon_2d
entity_forecast_icon_3: sensor.dark_sky_icon_3d
entity_forecast_icon_4: sensor.dark_sky_icon_4d
entity_forecast_icon_5: sensor.dark_sky_icon_5d
entity_forecast_low_temp_1: sensor.dark_sky_overnight_low_temperature_0d
entity_forecast_low_temp_2: sensor.dark_sky_overnight_low_temperature_1d
entity_forecast_low_temp_3: sensor.dark_sky_overnight_low_temperature_2d
entity_forecast_low_temp_4: sensor.dark_sky_overnight_low_temperature_3d
entity_forecast_low_temp_5: sensor.dark_sky_overnight_low_temperature_4d
entity_summary_1: sensor.dark_sky_summary_1d
entity_summary_2: sensor.dark_sky_summary_2d
entity_summary_3: sensor.dark_sky_summary_3d
entity_summary_4: sensor.dark_sky_summary_4d
entity_summary_5: sensor.dark_sky_summary_5d
Please help :)
following up on community discussion:
https://community.home-assistant.io/t/custom-dark-sky-animated-weather-card/59816/815?u=mariusthvdb
and create something like:
using:
this.cardinalDirectionsIcon = [
'mdi:arrow-down', 'mdi:arrow-bottom-left', 'mdi:arrow-left',
'mdi:arrow-top-left', 'mdi:arrow-up', 'mdi:arrow-top-right',
'mdi:arrow-right', 'mdi:arrow-bottom-right', 'mdi:arrow-down'
];
this is how I've now hard coded my example:
` var wind = this.config.entity_wind_bearing && this.config.entity_wind_speed ? html`<li><span class="ha-icon"><ha-icon icon="mdi:weather-windy"></ha-icon></span><span id="beaufort-text">${this.current.beaufort}</span><span class="ha-icon"><ha-icon icon="mdi:arrow-top-right"></ha-icon></span><span id="wind-bearing-text"> ${this.current.windBearing}</span><span id="wind-speed-text"> ${(this.current.windSpeed)*3.6}</span><span class="unit"> ${this.getUOM('length')}/h</span></li>` : ``;`
wouldn't mind splitting the line up to have it use an extra slot position, but as it is, is shows nicely compact
thanks for considering!
---update---
using this template (thanks to @petro) for customizing the sensor works as expected, maybe it would be useful for your card too:
sensor.dark_sky_wind_bearing:
templates:
icon: >
var icons = [ 'mdi:arrow-down', 'mdi:arrow-bottom-left', 'mdi:arrow-left',
'mdi:arrow-top-left', 'mdi:arrow-up', 'mdi:arrow-top-right',
'mdi:arrow-right', 'mdi:arrow-bottom-right' ];
var quadrant = Math.round(Number(state)/45);
if (quadrant < icons.length) return icons[quadrant];
return 'mdi:arrow-down';
Looks like darksky sensors entity_id's have changed.
Edited a few entities
entity_forecast_high_temp_1: sensor.dark_sky_daytime_high_temperature_1d
entity_forecast_high_temp_2: sensor.dark_sky_daytime_high_temperature_2d
entity_forecast_high_temp_3: sensor.dark_sky_daytime_high_temperature_3d
entity_forecast_high_temp_4: sensor.dark_sky_daytime_high_temperature_4d
entity_forecast_high_temp_5: sensor.dark_sky_daytime_high_temperature_5d
entity_forecast_low_temp_1: sensor.dark_sky_overnight_low_temperature_0d
entity_forecast_low_temp_2: sensor.dark_sky_overnight_low_temperature_1d
entity_forecast_low_temp_3: sensor.dark_sky_overnight_low_temperature_2d
entity_forecast_low_temp_4: sensor.dark_sky_overnight_low_temperature_3d
entity_forecast_low_temp_5: sensor.dark_sky_overnight_low_temperature_4d
entity_pop_1: sensor.dark_sky_precip_probability_1d
entity_pop_2: sensor.dark_sky_precip_probability_2d
entity_pop_3: sensor.dark_sky_precip_probability_3d
entity_pop_4: sensor.dark_sky_precip_probability_4d
entity_pop_5: sensor.dark_sky_precip_probability_5d
entity_current_text: sensor.dark_sky_current_text
but getting stucked on this one
which is in the config as
entity_daily_summary: sensor.dark_sky_daily_summary
nvnm found the fix
see thomasloven/lovelace-card-tools@1cf927a
I tried to create a PR but couldn't
Change line 4 to:
var LitElement = LitElement || Object.getPrototypeOf(customElements.get("home-assistant-main"));
Whenever i add the card in v 0.84 im getting this error
Keep getting 0:0:0 Uncaught
- type: module
url: /local/custom_ui/dark-sky-weather-card.js?v10
Hi,
thanks for your work. I have done as described (hopefully) but get this error massage.
http://hassio.local:8123/local/custom_ui/dark-sky-weather-card.js?v=8:1:8 Uncaught SyntaxError: Unexpected token {
Anyone else experiencing the custom card erroring out when accessing homeassistant (hassio .98.4) through an nginx proxy and duckdns.org?
Works fine as soon as I VPN in and use the local host name for my hassio install.
When:
When inserting template for dark_sky_current_text:
What:
YAML Error: YAMLException: missed comma between flow collection entries at line 58, column 27: value_template: {% if is_state("sensor.dark_sky_i ... ^
Note:
When I try to paste the template to template editor it works. But when I insert it directly to the card it does not. The dark_sky_alt_wind:
example works with no problem.
Here is PasteBin link to whole card: https://pastebin.com/E81wLR0g
Can you please look at it? Thank you very much 😄
I override the current text with basically Today's forecast. Without a width declaration the span extends into the temperature.
Example current_text:
Overcast High 67.5 Low 53.2 Heavy rain starting in the afternoon, continuing until evening.
Thanks for the great card.
I've read this
But I still have hard times to make it work.
any hints?
my ui-lovelace.yaml looks like:
title: My Awesome Home
resources:
- url: /local/custom_ui/dark-sky-weather-card.js?v=7.1
#- url: https://unpkg.com/@polymer/lit-element@^0.5.2/lit-element.js?module
type: module
views:
- title: main
icon: mdi:home-outline
cards:
- type: 'custom:dark-sky-weather-card'
title: Test
I have placed my icons in a different directory, but they still should show with the provided path in the card setup. These icons display if I select them inside the directory. I am thinking the weather card is configured to point at the path that's detailed in the install, but I didn't set it up that way (folder/syncing issues). Where in the card file does it specify the icon path?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.