-
-
Notifications
You must be signed in to change notification settings - Fork 937
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
ERROR ENOENT: no such file or directory, copyfile #3229
Comments
It's no use to reinstall by deleting node_modules and G:.pnpm-store |
|
🚢 5.18.6 |
having this issue in v7.1.3 |
In that case create an issue with steps to reproduce. |
I fixed it by deleting the store folder |
Also having this issue after upgrading to v7. I have no idea how to reproduce it though... it works again by nuking the whole store and re-downloading everything.
This is in MacOS by the way. |
I have the same issue in v7.3.0 |
v7.3.0
|
Just faced this again:
It's unfortunate that pnpm has gotten more unstable on the last two major versions or so with those random errors, as this was one of the biggest selling points compared to npm and yarn. |
These issues are unrelated to the original issue, which was fixed. You should create a new issue. |
New issue #4997 |
ERROR ENOENT: no such file or directory, copyfile 'G:.pnpm-store\v3\files\7f\188a9f33488e2f925682fff6cc2d5ec7c6face60dc5c59ef3662fa00f11d1f327ee44167904f4ed2c3a22ff0974fe331a4e9510680d2858da08dc7bf19d86f' -> 'G:\viz\std-3d-charts\node_modules.pnpm\jsdom@0.2.9\node_modules_tmp_33624_ce6506f720dd13db6952d1f74e1841d1\test\level3\core\files\orig\index.html?C=D;O=A'
at pnpm\jsdom
Progress: resolved 710, reused 0, downloaded 710, added 661
pnpm --version
5.18.3
node -v
v12.18.3 windows 10
The text was updated successfully, but these errors were encountered: