I don't have a test case at the moment, but I believe running webpack with multiple configs, whether using separate plugin instances or a single plugin instances shared across all configs, causes this plugin to report that nothing has changed when files have in fact changed.
And looking at the cache file, only one config file's dependencies and outputs are listed with mtimes.
I worked around this by doing one of two things:
- using a separate cache folder for each config
- using the same cache folder, but adding different data to the
cacheIdentifier key that is unique to each config.
Most other plugins don't really have this issue, so it would be nice to either work around it, or document multi-compiler usage.
By the way, thank you so much for this plugin! Now that it's working it removes 1.5 minutes off an incremental build!
I don't have a test case at the moment, but I believe running webpack with multiple configs, whether using separate plugin instances or a single plugin instances shared across all configs, causes this plugin to report that nothing has changed when files have in fact changed.
And looking at the cache file, only one config file's dependencies and outputs are listed with mtimes.
I worked around this by doing one of two things:
cacheIdentifierkey that is unique to each config.Most other plugins don't really have this issue, so it would be nice to either work around it, or document multi-compiler usage.
By the way, thank you so much for this plugin! Now that it's working it removes 1.5 minutes off an incremental build!