-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Consider ^ over ~ for default --save option #1123
Comments
npm are implementing this feature by the looks of it: npm/npm#4587 |
👍 |
👎 While semver seems to be quite popular in NodeJS land, some big browsers libraries don't follow semver. Marionette now defines explicit version ranges for its third-party dependencies. Backbone releases can make your whole app can fallover if you're using If you don't agree with the above, maybe consider that pre v1.0.0 dependencies are free to break BC, so avoiding fuzzy matching on those may be desirable. |
Pre 1.0.0 only matches patch version even with ^, so no change there. Please read https://github.com/isaacs/node-semver#ranges If you use Backbone or Marionette just hardcode the version yourself. Bower doesn't and won't care about libs not following semver. |
👍
That is the solution, still a bit of a trap for unsuspecting devs though. Marionette follows semver, just Backbone/Underscore don't :( |
I'm only agreeing on this if bower itself will change all The reality is good part bower component authors don't know what they're doing. You can't expect of them to know what is the difference between If you look at npm issue they have problems with it now. I think this should be closed. |
Especially bower doesn't have lockfile.. |
I guess this was fixed by: #2145 |
Currently bower install --save uses ~ in the dependency, consider changing to ^ for better semver compatibility?
The text was updated successfully, but these errors were encountered: