Open ValeryVS opened 5 years ago
You don't need cache-loader
on file-loader
, why you do this? Anyway it should works, please create minimum reproducible test repo, thanks
I encountered the same problem with this config:
{
test: /\.(jpe?g|png|gif)$/,
loaders: [
'cache-loader',
urlLoader,
isProduction && imageLoader,
imageSizeLoader
].filter(Boolean)
},
The comment from @evilebottnawi helped me to realize it should be this:
{
test: /\.(jpe?g|png|gif)$/,
loaders: [
urlLoader,
'cache-loader',
isProduction && imageLoader,
imageSizeLoader
].filter(Boolean)
},
@evilebottnawi It might a good idea to mention in the readme that it should not be placed before any loader that has side effects like emitFile
.
You don't need
cache-loader
onfile-loader
, why you do this? Anyway it should works, please create minimum reproducible test repo, thanks
It's needed if you have expensive plugins for optimizing images or other assets.
You don't need
cache-loader
onfile-loader
, why you do this? Anyway it should works, please create minimum reproducible test repo, thanks
https://github.com/Akiq2016/test-cache-loader here is my minimum reproducible test repo
Please migrate on https://webpack.js.org/configuration/other-options/#cache
Expected Behavior
file-loader
outputs all to assets folder.cache-loader
used withfile-loader
. While using withfile-loader
, if output directory does not content assets folder — get those files from cache and put in assets folder.Actual Behavior
Webpack doesn't output assets folder, that shoul be generated by
file-loader
.Code
How Do We Reproduce?
Add
cache-loader
beforefile-loader
.