search

erikflowers / weather-icons

215 Weather Themed Icons and CSS
https://github.com/erikflowers/weather-icons
6.89k stars 849 forks source link

Release latest on npm #206

Open moshen opened 6 years ago

moshen commented 6 years ago

2.0.10 is on bower, but not npm

benavern commented 6 years ago

Is this planned to push it on npm ? I'd realy enjoy using the last version but would like it to be on npm (don't want bower just for 1 library...)

timaschew commented 5 years ago

Usually you can install from GitHub via npm with this command

npm install erikflowers/weather-icons

but for me (npm 5.6.0) it doesn't work for some reasons. So, I pushed it to weather-icons2 on npm, anyone else can use this, too:

npm i weather-icons2
ManticSic commented 5 years ago

Usually you can install from GitHub via npm with this command

npm install erikflowers/weather-icons

but for me (npm 5.6.0) it doesn't work for some reasons.

Use this flavor:

npm install git+https://git@github.com/erikflowers/weather-icons.git

or this flavor if you need SSH:

npm install git+ssh://git@github.com/erikflowers/weather-icons.git

Tested with npm 6.9.0

abraha2d commented 5 years ago

@erikflowers Any plans to release v2.0 on npm? Edit: Nvm, looks like it's up under a different package name. https://www.npmjs.com/package/weathericons. Relevant pull-request: #133

aitorllj93 commented 2 years ago

Hi, I just noticed there are too many unofficial releases of this package because the package.json points to an old version package, do you have any plans on releasing latest versions under the official name (weather-icons) or change the package.json name and/or add some install instructions to the README?

fox91 commented 2 years ago

Hi, I just noticed there are too many unofficial releases of this package because the package.json points to an old version package, do you have any plans on releasing latest versions under the official name (weather-icons) or change the package.json name and/or add some install instructions to the README?

Hi @d3v0ps, currently version number in package.json have some problems (ex: not aligned with git tags). I'm working on v3 and I plan to move the repo (and maybe also npm package). As said by @ManticSic I currently suggest to install directly from this repo.

aitorllj93 commented 2 years ago

Hi @fox91 thank you for your response, I think this should at least be written on the README to avoid people creating forks and packages on npm when they aren't able to find the right one. There isn't even an installation section with the bower instructions.

fox91 commented 2 years ago

Hi @d3v0ps, would you like to create a PR with instructions on how to do it? Thanks