-
Notifications
You must be signed in to change notification settings - Fork 69
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
ocLazyLoad angular dependency version wildcard not being recognized? #263
Comments
|
I think I can't upgrade to backbone 1.3.3 because I use backbone.babysitter. |
@milk1000cc you are correct, it does. See here: https://github.com/npm/node-semver/blob/master/semver.js#L967 Although we're not using We'd gladly accept a pull request for this. The code you'd have to touch, unfortunately, looks like this: https://github.com/tenex/rails-assets/blob/master/app/models/build/utils.rb#L41 :) and the two tests that needs changing are here: https://github.com/tenex/rails-assets/blob/master/spec/models/build/utils_spec.rb#L66 |
OK. I'll try to fix. |
I found Bower uses old semver. Current version of In semver v2, semver.satisfies('1.4.1', '<=1.4.x') // => false
semver.satisfies('1.4.0', '<=1.4.x') // => false
semver.satisfies('1.3.9', '<=1.4.x') // => true Since I wrote my PR to be consistent with the latest semver, it may have to be rejected once. |
Hey @milk1000cc thanks so much for your PR. You're awesome. It's really well articulated and you fixed something pretty surprising. Sorry for the delay in getting back to you; I've been really busy with client work. Now that you've discovered that Bower's semver is v2, would you say that it works as designed currently? |
In master branch of rails-assets, I'm sorry I have no time to fix it now. |
ocLazyLoad currently has a dependency on angular (from here):
After upgrading to angular 1.4.1, we cannot get the latest ocLazyLoad. Looking at Gemfile.lock, it looks like the dependency is requiring angular <= 1.4. So, the wildcard version format they're using doesn't seem to be recognized by rails-assets.
The text was updated successfully, but these errors were encountered: