-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
Could not create _export folder: EEXIST: file already exists #68
Comments
That's unfair! I'll take a look into that ASAp |
Hi, having the same in vercel deploy. Something in their env? Installed by yarn 1 |
The problem is in our install script which fails on fs exists. What I can think of the following workaround – remove all the folders on preinstall script. E.g. preinstall: "rm -rf node-modules/odiff-bin" |
I will work on several odiff fixes on thanksgiving weekends and will fix the issue |
Thanks! |
The workaround of adding |
FWIW, I started seeing this today in our Netlify builds and once locally. We're using [email protected] (which uses [email protected]) and have been for a few weeks before seeing this for the first time. |
Need to revisit that one, workaround should help. Remove node_modules/odiff before you do npm install on CI |
The preinstall script wasn't enough for us for some reason. We use yarn, so pinning the version to 2.5.1 via the resolutions feature has worked so far |
It would be very helpful if you can create isolated repository specifically for your issue so I can debug it |
I can replicate it by initializing an empty package with |
This should be totally resolved by the new build system |
I've been using this with lost-pixel, and it gives me this error sometimes when I deploy to vercel and it uses the existing node_modules folder when reinstalling dependencies:
The text was updated successfully, but these errors were encountered: