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
Remove moot version
property from bower.json
#455
Conversation
i think i'll just drop explicit bower support next release |
|
I salute your bravery sir. |
Take this post as curiousity, not as "the inevitable backlash". What is the reason to remove bower support? Is it because with bower you can explicitly reference the git repo? |
There is no need for The inevitable backslash seems to be from the ones that rely in some features from |
Sad to see Bower support go away. I don't agree that this is the way to go. But I understand that having to support multiple package managers takes some time. I know I'm still able to fetch packages with Bower directly from the Github repo. So I can still use Bower. But I really don't understand those who prefer to use npm instead of Bower. IMHO npm is only for Node packages. I use it mostly for all build scripts. It just feels wrong to keep front end assets like css-files in the node_modules folder, together with mostly development/server code and build scripts. In some projects, its also useful to commit Bower components into the repo. I guess the chances to re-add Bower support is minimal, so I don't open a new issue on this topic, but I write here in this thread to express my opinion on this topic. Not all of us developers likes the current trend of moving away from Bower to npm. |
@olach |
Per bower/spec@a325da3