Update npm package version

[Va1]

Just ran into a fact that in npm the package version is still 1.3.2. Can you, please, publish he latest version there?

[erikflowers]

I am not sure how to do this one as there's not a npm file like the bower one. I am not even sure how it was added to npm. Where should I start to look?

[erikflowers]

I looked in to it - still confused. I don't recall ever making an NPM user or submitting this to NPM, someone else might have done it and made a PR and now I've removed it somehow. I will keep looking but feel free to help guide.

[Va1]

Here is the dude who did a npm package for weather-icons. I think, you can email him and ask to update the package or transfer it to your npm account. He does not maintain the repo nor the package, so this seems adequate to me.

[tbranyen]

Hey @erikflowers I'd be happy to transfer the package to you. Can you let me know your NPM username?

[erikflowers]

It is erikflowers. Thank you.

[jaapz]

So any update on this @erikflowers, @tbranyen? Would be nice to get this out of the way so we can depend on the official npm package again.

[erikflowers]

I don't see it transferred yet. I have no idea how owning a NPM package works. Once it gets moved, I'll probably set up the update to go along with all the other new icons that needs to be drawn and added, and then there's something up with the NOAA I don't quite understand.

At this point, the developers who are using these icons knowledge of how the "programming" and repo management of this project has surpassed mine, so things are slow on my end.

[tbranyen]

@erikflowers not sure why the transfer didn't work before. I've only just seen this issue (GitHub notifications suck). I've transferred the ownership to you and removed myself.

You should be able to just npm publish to update the package. Just make sure the package.json name matches weather-icons.

[ssc-hrep3]

Any updates on this issue? I recently switched from bower to npm for the dependency management and this is the only package which is missing on npm until now..

[MaxArt2501]

I'd like to ping this issue too.
If there are problems in transferring the package, drop a line to NPM support or even send them a tweet. If both parts are willing, there shouldn't be any problem.

[tbranyen]

I just re-ran:

npm owner add erikflowers weather-icons
npm owner remove tbranyen weather-icons

It should definitely be handed off... ping @erikflowers and he should be able to publish updates.

[jaapz]

@tbranyen npm still says you are the owner, although npm owner ls weather-icons shows erikflowers as the owner now.

$ npm owner ls weather-icons
erikflowers <{{eriksemailadress}}>

So maybe the owner updates whenever @erikflowers pushes a new version?

[jaapz]

@erikflowers are you able to push a new version to npm now?

[avilao]

I'd also like this please.

[TheSharpieOne]

https://www.npmjs.com/package/weathericons seems to be the updated package.

[MaxArt2501]

That's odd, because package.json clearly shows that the name is "weather-icons", with a dash.

[TheSharpieOne]

It's one of those "The author doesn't want to update it so I will" scenarios where someone else has published a more up-to-date package with a slightly different name.
Plus, there is reference to that package in a PR.