"Nowadays, Bower is the most popular package manager"

[lastmjs]

This page recommends Bower as the most popular front-end package manager. I think it is agreed that this is changing. I know Polymer is in the process of switching, see this issue and this issue. Just wanted to bring up a potential change in wording as the switch to npm seems to be imminent. It would be nice to perhaps explain this situation a little bit, instead of continuing newcomers' faith in Bower as the best package manager moving forward.

[Nevraeka]

@lastmjs Today because of the issues you cited - Polymer has no choice but to use Bower. That is not to say that you can't use JSPM or NPM for other web components. @RevillWeb is using JSPM/System for his vanilla components. I'm using NPM/WebPack & Bower (for Polymer) for mine so I think this is still relevant. I'd love to read a blog post on the ways we load these components from various package systems. Maybe we can reword the page a bit better to suggest more options without making it a giant post on package management and implementation cases. thoughts?

[Nevraeka]

Also customelements.io currently uses bower for discoverability....sadly

[lastmjs]

Maybe something like: "Currently most web components libraries have great support for Bower, that's why we recommend you to use it. Keep in mind that Bower is not the only package manager for front-end code..." and then perhaps very briefly explain the role that NPM is/will be playing in front-end package management?

[zenorocha]

@Nevraeka CustomElements.io fetches both bower and npm packages since last year.

@lastmjs could you send a PR with this change?

[Nevraeka]

Thank you @zenorocha for clarifying. Good to know

[lastmjs]

@zenorocha I'm on it