You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On line 246, the directory would have had to exist, otherwisedestFiles would not have been successfully instantiated
Once it (asynchronously) reaches lines 254, one of the folders referenced in destFiles no longer exists and causes the lstat to fail. I suspect it no longer exists due to workspace hoisting
If the current behavior is a bug, please provide the steps to reproduce.
Suspect that this bug only occurs in large dependency graphs. Running the same command again gets it work?
What is the expected behavior?
For yarn install to complete successfully. Race conditions need to be identified and removed
Please mention your node.js, yarn and operating system version.
node v11.7.0
yarn v1.13.0
macOS 10.14.2
The text was updated successfully, but these errors were encountered:
this is an issue for me.. I have a large dependency graph (because of @angular and @nestjs packages) and continuously run into this error when running yarn install.
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
yarn add <pkg>
in a package of a workspaces structure fails, with ENOENT, due to yarn attempting tolstat
on a folder that has been hoisted.This is the
lstat
in question:yarn/src/util/fs.js
Line 254 in 158da6c
destFiles
would not have been successfully instantiateddestFiles
no longer exists and causes thelstat
to fail. I suspect it no longer exists due to workspace hoistingIf the current behavior is a bug, please provide the steps to reproduce.
Suspect that this bug only occurs in large dependency graphs. Running the same command again gets it work?
What is the expected behavior?
For
yarn install
to complete successfully. Race conditions need to be identified and removedPlease mention your node.js, yarn and operating system version.
node v11.7.0
yarn v1.13.0
macOS 10.14.2
The text was updated successfully, but these errors were encountered: