Polymer on NPM stuck on version 1.2.5

[lukasoppermann]

Hey,

could you please publish 1.6.1 to npm? Thanks.

[ebidel]

This is something we need to do for 2.0!

[d4l3k]

Can we at least push v1.7.0 to NPM?

[reicruz]

Has this gotten any attention to push the latest version? Or are you waiting until 2.0 to publish a new version on npm?

[madeleineostoja]

Bump. We're aiming for full Yarn support for our components to start moving away from Bower but not being able to pull in Polymer as a peer dep is stopping us from doing that. Is there anything blocking publishing 1.7 to NPM (for Yarn)?

[justinfagnani]

The client-side packages in the @polymer scope are still experimental as of now. We're trying to ready all the pieces that will let published fully supported packages, but we're not there yet. We're focused on getting 2.0 out the door, and then npm/yarn support will be top priority.

[pomber]

2.0 is on NPM

[leogr]

Is it still experimental?

[madeleineostoja]

Also looks like all the other packages in the @polymer scope are still alpha versions (0.0.x) - is there a timeline to bump those?

[pomber]

Is it still experimental?

Yes

[mrjoops]

Recently, while installing polymer2 through npm, the following message was brought to my attention:

...psst! While Bower is maintained, we recommend yarn and webpack for new front-end projects!

This message appears since late may as a npm deprecated message, and also on the bower.io and in it repo README.

Obviously it's not an easy task since the documentation and the starter kit heavily depends on bower, and Polymer/polymer is not the only repo to update, but migrating to npm seems the way to go.

[web-padawan]

@mrjoops please see #326 - it is the original issue to track npm progress

[TimvdLippe]

Closing this issue per #326 (comment) @polymer/polymer is now maintained on NPM since version 3 🎉