-
-
Notifications
You must be signed in to change notification settings - Fork 78.9k
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
Drop Bower support #23568
Drop Bower support #23568
Conversation
Asked Twitter to weigh in :D. I'm unsure on overall usage—I don't think Bower ever had install stats like npm does on their packages. Hard to know how used it is. |
I vote: "drop it". |
Drop it vote! |
drop it |
Drop it |
keep it |
If it means Bootstrap having multiple npm packages, I'm all in for dropping bower. |
@chyvak1831 I feel like the argument for dropping is there. Do you have an argument for keeping it? |
I happen to use Bootstrap via Bower but would be happy to hear of a better way to proceed. |
Keep it |
Drop it. There's no need for it to exist anymore. It's better for everyone to focus entirely on npm. |
Drop it |
1 similar comment
Drop it |
Drop it like it's hot |
Dracarys |
Drop it |
Drop it. It's been abandoned and practically superseded by npm for a while now. |
So @mdo it seems most people are in favor of this. Only concern is VS? |
Drop it |
3 similar comments
Drop it |
Drop it |
Drop it |
drop |
Drop |
Drop It! |
@tkrotoff That's just blatantly invalid JSON to make it clear that Bootlint deliberately doesn't support Bower. If there wasn't a bower.json, I'm sure we'd get pull requests adding one or issues asking for one. |
Keep it. |
keep it |
Drop it npm is better. |
Drop it. |
There's so many fundamental issues with bower that, even if it causes breakage in cases, even for myself, I'd vote drop it. We'll fix those cases and move the whole ecosystem to brighter future with npm catering to all our packaging needs. If twbs sets this example I'm sure many will follow suit 👍❤️ |
I vote drop. Bower is kind of dead to me nowadays. |
Keep. I still use bower. |
I'd decide based on the workload it creates to still support Bower. It's always nice to keep backwards compatibility, however if it involves some serious work on your end and is possibly blocking a more modular approach (which could likely be achieved with Bower as well?!) I'd say go with npm/yarn instead. |
Bootstrap 3 will continue to be available with Bower. This only applies to v4. If you have an old project, this changes nothing. And Bower is deprecated, really:
To all people who replied "Keep it", why? |
Does dropping Bower also mean that all the compiled code in |
We use our dist files for our documentation too, so they'll stay if we drop Bower |
As we're also advising people to use yarn/webpack for new projects, this sounds like a neat solution. 👯 |
I vote for keeping Bower support. |
Please drop it. |
Drop it. |
Bower is deprecated.
See bower/bower#2298
Dropping Bower will allow to split Bootstrap in multiple npm packages, see #23557 (comment) and following comments.
Ping @XhmikosR