Replies: 1 comment
|
You can use |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We all know that when the configuration file for webpack changes, the entire file system caching gets invalidated.
In our case, the configuration file needs to change very frequently, essentially each change in source code would imply a change in config file, so does this mean we can't benefit from file system caching at all?
Specifically, the changing config only affects one specific loader (babel-loader). Would be curious to know if we can configure it so that we can still cache & speed up other loaders prior to babel-loader (like ts-loader) using the file system caching?
All reactions