-
Notifications
You must be signed in to change notification settings - Fork 510
Support for angular 1.4 #195
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
Comments
Well it's supposed to work, isn't it the case? |
Bower.json is not supporting 1.4.0. Please update bower file instead. Can than test it |
Well it does: Check it here: http://semver.npmjs.com/ |
This is what I get from bower install: |
Did you clean your bower cache ? |
I did the last one :-) |
Good. I'll take a look at this when I have the time, because it should be working with this expression. |
Same issue for me.
In my bower.json I have this line : "angular": "~1.4.3", and "oclazyload": "~1.0.4", I executed the Thanks for your help! |
Well that's weird, because the semver expression is valid, bower may not follow the npm syntax properly... ? |
OK ! |
Re-reporting same problem. I'd suggest that using 'x' in comparisons, as in "<=1.4.x", is unusual, at the very least. A brief search found no example of use or specification of how it would be interpreted, including at https://github.com/npm/node-semver . I'm a noob, though! If anyone needs a quick fix, e.g., for heroku deployment, add a "resolutions" section (a peer to "dependencies") to your project's bower.json, forcing what you need, e.g.:
This will quell messages like
|
Please support angular 1.4 |
Yes I'll be back from my holidays tomorrow, I'll do it this week end. Sorry |
Thanks ocombe. |
Ok I changed it to >=1.2.0, let me know if it works (once I released a new version) |
Could you please provide support for 1.4 as it is out now and major libs are providing support for it.
The text was updated successfully, but these errors were encountered: