-
-
Notifications
You must be signed in to change notification settings - Fork 451
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
Recover from EROFS #327
Comments
Thanks for reporting. |
I think it would work, and it would be better than my suggestion of no caching. Thanks! |
Is there any update or timeline on this? |
I spared some time to fix this myself, can you check it out? |
* fix cache directory not writable (#327) * Fix directory fallback Only fallback for non custom directories Also fallback if writing fails * add tests * Disable tests, as they screw up node 0.10 * Remove mock tests I cannot manage to get that reliably working, somehow mock-fs is messing up ava/mkdirp/rimraf and makes ava hang forever on error
Awesome, thanks! Now we need a release so create-react-app can use it and they can make a release. |
I'm submitting a bug report
I'm submitting a feature request
Webpack Version:
1.13.2
Babel Core Version:
6.17.0
Babel Loader Version:
6.2.7
Please tell us about your environment:
Linux
Current behavior:
Fails if target
node_modules
directory is read-onlyExpected/desired behavior:
It should recover and should disable caching
node_modules
read-only (in my case, it's generated this way by a build tool)What is the expected behavior?
It should run, without caching
What is the motivation / use case for changing the behavior?
I know this is not the common use case, but out build process depends on Nix package manager, which fetches and builds node dependencies for our project in a read-only directory. When I try to run dev server, it fails since
node_modules/.cache
is read-only. I want it to recover as best as it can.The text was updated successfully, but these errors were encountered: