-
Notifications
You must be signed in to change notification settings - Fork 59
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
Astroturf causes errors when using persistent caching with Webpack 5 #681
Comments
@jquense Ahh, just found your long-running issue in webpack/webpack#11074 ... Looks like a few other pieces of tooling have had success moving away from virtual modules (marko-js/webpack#48, sveltejs/svelte-loader#151) in the past month or so, maybe there's a more obvious way forward now? |
hmm i'm now very confused as to why our app doesn't exhibit this problem, thanks for the repro repo. I've considered the other approach in that issue but there are a lot of downsides to it that seem untenable but i need to try and spike it out again to see. |
I'm hitting this as well. |
@jquense so just add |
nice! |
As discussed in #667.
Astroturf will cause errors when using Webpack 5's persistent cache. It wouldn't bother me too much if persistent caching simply didn't work for Astroturf, but as it stands these errors block the use of persistent caching entirely and require the user to turn it off. I thought I'd file a separate issue for this since #667 seems to concern persistent cache support for Astroturf, whereas this is about a blocking error.
Here's a minimal repro: https://github.com/lostfictions/repro-astroturf1-webpack5
To reproduce:
yarn install
yarn start
and open http://localhost:8080/ in your browser. Everything should work fine.node_modules/.cache/webpack
.Looks like it's trying to find materialized versions of the virtual modules, presumably to check whether they've changed and the cache needs to be invalidated. I'd hazard a guess this could be fixed by telling the cache manifest to check the original source files (ie.
index.js
in this case) instead.The text was updated successfully, but these errors were encountered: