-
Notifications
You must be signed in to change notification settings - Fork 20.6k
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
Build: drop bower; use npm for front-end deps #1620
Conversation
Fixes #15186 Closes jquerygh-1620
npm is better? |
Fixes #15186 Closes jquerygh-1620
@rsantostray One package manager to rule them all. |
Bower doesn't bring anything npm cannot do except being less reliable & solid. A huge 👍 from me. |
Just to be clear, this is for our internal dependency management. We will continue to support installing jquery with bower. |
sizzleLoc = __dirname + "/../external/sizzle/dist/sizzle.js", | ||
rversion = /Engine v(\d+\.\d+\.\d+(?:-\w+)?)/; | ||
|
||
require( "colors" ); | ||
|
||
/** | ||
* Retrieve the latest tag of Sizzle from bower |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems that comment must be changed too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
Fixes #15186 Closes gh-1620 Conflicts: bower.json
Fixes #15186 Closes jquerygh-1620 Conflicts: bower.json
No need for bower anymore.