-
Notifications
You must be signed in to change notification settings - Fork 254
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
unversioned dependency problem on locked dependencies project #44
Comments
Hi @atilafassina, thanks for your report. First of all, I have to say that I have no clue of shrinkwrap at all and I didn't test it during development. Furthermore, when I was writing svg-sprite at around christmas, lodash was available in version 2.41, but I was relying on functionality that would be introduced with the upcoming v3.0, so I had to use the unversioned dependency to enforce the use of the latest sources from GitHub. I just realized that the v3.0 of lodash is available since monday, so I'll happily go and update my dependency as soon as possible. I'll push out another release probably tonight or tomorrow. Cheers, |
wow! Thanks a lot, @jkphl After your commit, I'll test again and post the feedback here... |
You're welcome. Well, it looks like there's no official v3.0 NPM package yet. Will need to wait for that one. Stay tuned. ;) |
👍 ok! |
Seems we'll have to wait until next Monday: https://twitter.com/jdalton/status/558308326862098432 |
Yeah... took some while more, |
Thanks for the heads up. Will try to push out another release tonight! :) |
👍 thanks a lot! |
The new release is out — hope this works for you now! :) |
It did the trick! 🎉 |
You're welcome! Thanks for the feedback. :) |
Hello!
I might a problem using svg-sprite with grunt-svg-sprite when locking dependencies with npm shrinkwrap
on
package.json
, line 38 there's defined lodash as a dependency without versionOn
grunt-svg-sprite
dependencies, it generated with agit+https
path, that would download any version, as far as I understand... possibly breaking the plugin if any major changes happen.And, after locking dependencies with shrinkwrap it generates a relative path that's not working when I'm testing on different environments.
Does this all makes sense to you?
If so, I imagine the simplest solution would be to determine a version for lodash here, right?
The text was updated successfully, but these errors were encountered: