fix: resolve custom commonSourceDir before setting up watch plugin #235
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes at least one of the issues in #84 that was affecting my project—the
WatchFilterPlugin
is set up to rely on absolute paths in order to behave as expected, and this breaks HMR whencommonSourceDirectory
is specified at all.Note: I have a setup that looks like this (common when using Lerna/Yarn workspaces in a monorepo):
In this case, I actually want my
commonSourceDirectory
to be".."
(I'm runningelectron-webpack
out of e.g.project/packages/electron-app1
), which fully breaks HMR. I considered adding a new config option likewatchDirectories: string[]
and changing the logic to not overload the meaning ofcommonSourceDirectory
, but I think this is clean enough for all the use cases I can think of. @develar, please LMK if you prefer something else!