search

Polymer / polymer

Our original Web Component library.
https://polymer-library.polymer-project.org/
BSD 3-Clause "New" or "Revised" License
22.04k stars 2.02k forks source link

Polymer on NPM stuck on version 1.2.5 #3903

Closed lukasoppermann closed 6 years ago

lukasoppermann commented 8 years ago

Hey,

could you please publish 1.6.1 to npm? Thanks.

ebidel commented 8 years ago

This is something we need to do for 2.0!

d4l3k commented 8 years ago

Can we at least push v1.7.0 to NPM?

reicruz commented 7 years ago

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 commented 7 years ago

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 commented 7 years ago

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 commented 7 years ago

2.0 is on NPM

leogr commented 7 years ago

Is it still experimental?

madeleineostoja commented 7 years ago

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 commented 7 years ago

Is it still experimental?

Yes

mrjoops commented 7 years ago

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 commented 7 years ago

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

TimvdLippe commented 6 years ago

Closing this issue per https://github.com/Polymer/polymer/issues/326#issuecomment-387910751 @polymer/polymer is now maintained on NPM since version 3 🎉