Replies: 2 comments 5 replies
-
Do you have warnings/errors when you set |
Beta Was this translation helpful? Give feedback.
-
Hi @alexander-akait!
No. I think I figured out what the issue is. Here's an example that replicates it: https://stackblitz.com/edit/github-nb6ybc-5qrl4h?file=webpack.config.js (I updated this link, as I think the previous one linked to a wrong project). We have a third-party CSS code ( However, for some reason it breaks webpack cache (de)serialization. It didn't work for us with Please let me know if it's better to create an issue for this. |
Beta Was this translation helpful? Give feedback.
-
Hi!
Our development builds are really slow, so I thought about using built-in persistent cache and switch it from the default
memory
tofilesystem
. Unfortunately, it doesn't really seem to do anything and the startup time hasn't changed. I noticed the following errors (a lot of them) in the output:It looks like I'm getting this error for every file, JS, CSS, images, etc. :/ Any idea what it can be caused by? I'm not sure where the
null
part comes from inwebpack/lib/asset/RawDataUrlModule/null
.My cache config is simply:
cache: { type: 'filesystem' }
.UPDATE:
I removed all entrypoints and started adding them back one by one to see when it starts throwing these errors.
One cause that I found so far, is a CSS entrypoint (yes, we've got those) that imports a very old minified CSS file (
jquery-ui-1.10.0.custom.min
from 2013...) that includes somebackground-image: url(...)
declaration, where image paths point to non-existing images. If I remove this single import it works fine. When I add it, webpack starts reporting these errors.Beta Was this translation helpful? Give feedback.
All reactions