-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Scoped package installation sometimes fails on Windows #1861
Comments
Confirm: Running 0.17.2 the issue of 0.16.1 persists. Getting
on windows 7 x64 / node 6.9.1 Running yarn add a second time, it works. |
persists with 0.17.3
|
Also seeing it with 0.17.4 |
@maybeec, @ecozoic: If this is blocking you at the moment, it's possible to work around if you have some control over your dependency tree. There's a complete description of the underlying problem on this PR, but the TL;DR is that all subdependencies of the scoped dependency must be hoistable. So, the scoped dep can't share any semver-incompatible subdependencies with the rest of the tree. |
After working on some other workarounds of yarn bugs, I came back to this issue. Unfortunately, I currently also cannot run a successfull build of |
ok, after some debugging, I found the same things @dpoindexter already fixed. |
Considering that branches diverged too much let's make a 0.18 release later this week |
@bestander That would be excellent. This is the last remaining issue preventing us from moving fully to yarn. |
That sounds nice, I would love to see this release this week as it would be best fitting to my upcoming rollout next week. |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
When a project depends on a scoped package on Windows, the package linking step fails 50% of the time if any subdependencies of the scoped package aren't hoisted out of the scoped package.
If the current behavior is a bug, please provide the steps to reproduce.
yarn add
a scoped package (ex.@cycle/http
)yarn add
any dependency of the scoped package, at an incompatible version (ex.superagent@1.7.0
) (This prevents the subdependency of the scoped package from hoisting)yarn add
a second timeWhat is the expected behavior?
Running
yarn add
again for the same package should successfully complete and re-link packagesPlease mention your node.js, yarn and operating system version.
node: v6.9.1
yarn: v0.17.0
os: Windows 10
yarn-error.log
Arguments: C:\Program Files\nodejs\node.exe C:\Users\dpoindexter\AppData\Roaming\npm\node_modules\yarn\bin\yarn.js add superagent@1.7.0The text was updated successfully, but these errors were encountered: