A way to analyze why modules were flagged as "not cacheable".

[jussi-kalliokoski]

Currently I'm trying to reduce our massive build times in the watch loop, but I can't figure out why none of the modules are marked as cacheable. I've been trying to drop loaders and so on to see where the problem is coming from, but obviously if you omit a necessary step the build starts breaking so this hasn't gotten me too far.

It would be extremely useful if there was an easy way to see where the module(s) was/were flagged "not "cacheable", so one could potentially fix the misbehaving plugin.

[luisrudge]

👍 to this.

[ChihHaoTW]

+1

[wkentdag]

👍

[ghost]

👍

[trivektor]

👍

[narehart]

👍

[MartinDawson]

Why do people have to spam thumbs up? What on earth do you think the emoji is their for on the OP?

[ghost]

+1 = : +1 : (without the spaces) = 👍

It express the fact that people would love to see this feature, also it may act as a "bump".

I hope this explanation helped you.

Regards,

[IamTheHttp]

2 years later, I'm still wondering :)

[abhinavsingi]

What are the most common reasons a module is marked in such a way?
Can anyone tell? (before it's implicit in possibly future versions of webpack)

[aaronfrost]

Same issue. When I run the dev-server in watch mode, by simply adding a space to a file and saving, the webpack recompile takes quite a while. I am used to this being very quick in the past, at other jobs I've had. But here, when I simply change a space, it recompiles a tons of things, and outputs them all as [not cacheable]. Does anyone know how to find out why? @TheLarkInn do you have any tips to help us troubleshoot?

[aaronfrost]

OK. So, I found that one of my loaders was causing my JS files to be not-cacheable. Once I removed it, it worked. So... you can try to remove your loaders and see if that fixes it. Even if your app doesn't run, you should notice that things at least build and are cacheable. Once you find the bad-acting loader, you can then try to configure it to allow things to be cacheable.

[zhaomiing]

some issue, any idea pls

[AlisterC93]

Still no solution?

Come on guys, its 2017

[mindplay-dk]

Come on guys, its 2017

It's 2019 🤐

[webpack-bot]

This issue had no activity for at least three months.

It's subject to automatic issue closing if there is no activity in the next 15 days.

[alexander-akait]

bump

[rnacken]

Come on guys, its 2017 2022

[T1masv]

Still no answer its 2023 guys :/