-
Notifications
You must be signed in to change notification settings - Fork 37
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
null version detected for bower dependencies #13
Comments
This also seems to be a problem if the destination repo has no bower.json file. Such as: https://github.com/furf/jquery-ui-touch-punch I suspect if the folder exists, but no bower.json file exists we should likely just best-effort assume all is satisfied. |
I was not sure how to handle this. @stefanpenner I will try your suggestion. |
@quaertym Ya, I am not quite sure the best way either, maybe someone else has a better idea. For reference my solution/workaround was to merely "vendor" this dependency and commit it to my project manually. |
@stefanpenner 👍 for vendor approach but I think many users are not aware of it. We should cover this use case anyway. There is also a problem with static files that bower manages see this pr #12. |
Yeah, this bit us as well today. Ugly and more than a bit perplexing. |
I ran into this with an http dependency
Not sure if it's relevant, but I did notice that |
I ran into the same "sinon" issue ... and also now have a problem with antiscroll as installed by ember-cli-ember-table. Could someone explain the "vendor" workaround? I have got things working temporarily by simply deleting the reference in bower.json after I install, but this is obviously just a temporary patch for development. |
@amk221 @stefanpenner thanks for the suggestion. Is there any tooling support for vendoring a dependency or do I just need to put it in the I've got it working manually but it would be nice if there was a command I could run to update the package. |
When pulling a bower dependancy from a git url like: git://github.com/amk221/my-thing.git _#master_
the dependancy is determined to be 'not installed' (therefore builds fail).
It works without the #tag
The text was updated successfully, but these errors were encountered: