-
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
Error: ENOENT: no such file or directory, copyfile #5275
Comments
That's a strange one. Even after it errors, I can |
I was having a similar issue but worked around it by removing |
When I just tried to reproduce the bug, I got there error already during the "yarn add -E prisma-yml" step. The "no such file or directory" message was appropriate here since the target directory |
|
For what it's worth, I wasn't able to cure with the steps Markus suggests. I even tried reinstalling yarn and manually deleting the yarn cache using I did find a partial solution. I'm posting here in hopes it sheds light on what the underlying issue might be. Bullet 4 below shows how I fixed it. My situation:
And... the 5.0.2 directory was empty, which is why I was seeing the error.
So, although I can continue development, I suspect my CI is borked. Update: |
I had this today, and had to
|
This is still an issue, even in
|
still errs after Yarn version: Node version: Platform: Trace: fix with |
I found success by reinstalling yarn w/brew. |
Had the same problem upgrading to yarn 1.15.2. removing node modules and cleaning cache did the trick. |
This worked for me |
For those hitting this problem from inside WSL on Windows, this fixed it for me:
Installation succeeded, and switching back to an Ubuntu terminal (in WSL (inside VSCode)) I could |
This may not have anything to do with the issue here, but in case it helps, I have run across this issue when trying to copy files in between different volumes (especially NAS volumes) using the native fs routines. |
Yarn cache is not working as expected. Maybe related yarnpkg/yarn#5275
* Upgrade expo sdk to 43 and instsall deps * Upgrade @dooboo-ui/theme * Fix linting * Update test config and prevent breaking * Remove `resolution`, the types looks like fixed * Yarn2 renamed --frozen-lockfile into --immutable * Remove --frozen-lock Yarn cache is not working as expected. Maybe related yarnpkg/yarn#5275 * Install expo-cli in CI * Revert the expo/match-media package url * Upgrade @dooboo-ui/theme to 0.4.3 * Update yarn.lock * fix: added --network-concurrency to yarn install script Related yarnpkg/yarn#6312 * Fix linting * Warn react-hooks/exhaustive-deps instead of error Strangely some machine thorws different errors * Remove dup rules in eslint
I have this message from type to time when using Yalc to symlink folders |
I got the same problem. It started occurring in my CI after refactoring a lot of files WITHOUT doing any changes to the I'm unfortunately not able to share the repository since it is a private work repository. . However, I was able to solve it by having the CI run |
It looks like this is still a problem with |
yea ive been seeing this issue a lot lately |
version problem ? |
Started with:
Added below to User Environment variables
Then
Then since the issue was
Then did:
Then in VS Code, output, in dropdown, I saw error in
Then it worked, this was unexpected! |
I've tried the suggestion above and worked here |
Update:I think in my case it happened because the project was initially installed with pnpm, and I ran Hitting this error consistently today. Both locally on MacOS and on Ubuntu in CI: https://github.com/akd-io/create-next-stack/actions/runs/4772052085/jobs/8484361470?pr=172 local yarn-error.log:
|
Solved this same issue by changing the Docker volume flags from I hope this helps somebody! |
My solution was removing the file mentioned on the error after the word |
TL;DRIf all the previous solutions did not work with You, try this:
yarn config set "strict-ssl" false -g
|
Do you want to request a feature or report a bug?
bug
What is the current behavior?
When having a yarn workspace, adding one of the packages to another and then executing
yarn install
throws this error:Error: ENOENT: no such file or directory, copyfile '/Users/tim/Library/Caches/Yarn/v1/npm-jsonfile-4.0.0-8771aae0799b64076b76640fca058f9c10e33ecb/CHANGELOG.md' -> '/Users/tim/code/prisma-deployment-test/cli/node_modules/prisma-yml/node_modules/jsonfile/CHANGELOG.md'
Complete yarn-error.log
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
Execute
yarn install
without throwing an error.Please mention your node.js, yarn and operating system version.
yarn@1.4.0
node@9.4.0
macOS Sierra@10.12.6
The text was updated successfully, but these errors were encountered: