Why are so many [not cached] files recompiled with webpack?
I have a fairly small project. About 800 modules. When I change one of the files and webpack-watch recompiles everything, it takes much longer than I would like. And I think the main reason is that when it is done it lists hundreds of files [not cacheable]
.
There are hundreds of these files every time I save even a single char change.
Any ideas on what might be causing these files to not be cached? Any ideas on where I can start looking for this? I staggered and still have not been successful. The only downloader for my files .js
is ts-loader
. Other than that, I don't use any other bootloaders.
I just need ideas on where to start. This github issue has been around for years with no answer. People need help figuring out how to find out why a particular file is not being cached. Any ideas here would be much appreciated. I can show samples from mine webpack.config.js
. I'm on webpack 1 right now. I don't think this is a problem.
Tell me.
source to share
I don't have an answer that will resolve this for everyone. But, for my case, I used a bootloader which made my stuff non-cacheable. Once I fixed it, I felt good. The boot loader I used is mark-loader . Once I figured it out, all the files were cached again again.
source to share