Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move from bower to npm #111

Open
martin-s opened this issue May 21, 2015 · 2 comments
Open

Move from bower to npm #111

martin-s opened this issue May 21, 2015 · 2 comments

Comments

@martin-s
Copy link

I would like to propose to centralize package management to npm. So, packages in bower.json are moved to package.json as devDependencies.
What are the pros for bower? I would prefer to just use one single tool for package management. Wdyt?

@cgross
Copy link
Owner

cgross commented May 21, 2015

I'm open to moving to npm but now I believe more packages (front-end) are still published to bower than to npm. Thats changing but I'm not sure its at critical mass just yet.

I'm certainly not in love with bower.

@dancancro
Copy link

Hi all,

I've seen this question come up before and would like to know what exactly are the pros and cons of these. So I made a questionnaire. If you would like to fill it out, I'll add that knowledge to the central knowledge base of technology product features here and everyone will be able to easily see the trade-offs.

Click here to do the questionnaire. Choose Package Managers to describe Bower or NPM specifically.

Thanks,
Dan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants