webpack.js.org
webpack.js.org copied to clipboard
Document how managedPaths differs from immutablePaths
Feature to document
snapshot.managedPaths: https://webpack.js.org/configuration/other-options/#managedpaths.
https://github.com/webpack/webpack/pull/14509
Author(s)
@sokra
Additional information
It is not at all clear from the current documentation how managedPaths differs from immutablePaths. The documention for managedPaths just says:
An array of paths that are managed by a package manager and can be trusted to not be modified otherwise.
What does "otherwise" mean? Is there something which will trigger webpack to invalidate the cache for these files? If so, what? If not, how does this option differ from immutablePaths?
I would love to understand the same.
You might be able to glean something from https://github.com/webpack/changelog-v5/blob/master/guides/persistent-caching.md#performance-optimizations