Skip to content
This repository has been archived by the owner on Nov 23, 2021. It is now read-only.

remove bower #91

Open
maybeec opened this issue Mar 30, 2016 · 3 comments
Open

remove bower #91

maybeec opened this issue Mar 30, 2016 · 3 comments

Comments

@maybeec
Copy link
Member

maybeec commented Mar 30, 2016

We should remove bower as it does not provide any further benefit since npm catched up supporting everything bower has been added value for.

Would be worth a discussion to make live simpler especially in our sample, which already utilizes a lot technologies to work.

@dumbNickname
Copy link
Contributor

Totally agree! Bower does not bring any additional value, can even be a disadvantage as some people publish their plugins/packages/angular component or modules only in npm. I had such a situation when guys developing one of components that we decided to use abandoned bower in favor of npm - not a nice surprise when you need to upgrade to new version.

@mmatczak
Copy link
Member

Saying let's get rid of bower and let's go for npm! is easy, but after that you have to think about how to build your application and what module system to use. And making the right decision today is not easy. Browserify, Webpack, SystemJS with jspm - these are some of the options. The latter is my favorite. In my current project I use SystemJS with Bower (for some technical reasons).

@maybeec
Copy link
Member Author

maybeec commented Mar 31, 2016

I am also fine with jspm. However, I could not determine the big advantage of jspm over npm + browserify. Jspm seems to be the current hipe due to its extensibility and the out of the box support for all module styles.
Currently, I have not seen any killer argument to go for npm + browserify vs. jspm + systemjs.
You might even think of npm + systemjs.

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

No branches or pull requests

3 participants