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
Doesn't work with github branches #671
Comments
I'm having the same issue: excerpt from the package.json
Throws this error:
|
Same issue happens with other repository hosts, including bitbucket. EDIT: This is a dupe of #513 |
@onlywei it should work for your case if you follow #708. @tabrindle looks like in this specific case the slash is the culprit. If the branch has no |
I believe the |
I'm having issues despite the proposed workarounds, but I did find that pointing at the tarball fixed my problem. In my
However, the following attempts all failed:
To be specific, Yarn was able to clone the repo in the latter attempts -- but the code it used was not the correct branch. This was obvious because I kept getting either the following error:
or this one (which is what the branch
|
This has been fixed by a collection of fixed that have landed in master over the past 2 weeks. please reopen if you are still able to reproduce on master. thanks everyone. |
Because yarn bug causes head of branch not be fetched if there is already a cached version of the branch. See yarnpkg/yarn#671
v0.15.1
Do you want to request a feature or report a bug?
Feature? Bug? Not sure.
What is the current behavior?
I just tried installing yarn today for a spin, and immediately failed when I tried to execute
yarn
in my directory because I have this dependency listed in mypackage.json
:"istanbul": "gotwarlost/istanbul.git#source-map"
If the current behavior is a bug, please provide the steps to reproduce.
Just try running
yarn
with that listed in as a dependency or devDependency inpackage.json
What is the expected behavior?
Install?
Please mention your node.js, yarn and operating system version.
Node v6.3.1, Yarn v0.15.1, Mac OS X 10.11.6
The text was updated successfully, but these errors were encountered: