ISSUE 947 - plugins defined with webpack 3 _modules Set in a develope… #956
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.
Plugins defined with webpack 3
Chunk._modules
Set in a developer's parent project explode when run via webpack-dev-server, as dev-server actually starts and runs a webpack instance via its own dependency, which is currently 2.x . Bumping dependency to 3.x fixes this compatibility issue, and should be backwards compatible as the oldmodules
array is deprecated gracefully.What kind of change does this PR introduce?
Bug fix #947
Did you add or update the
examples/
?N/A
Summary
Fixes #947
An upgrade to webpack 3 in own project broke webpack-dev-server controlled builds, breaking our workflow
Does this PR introduce a breaking change?
Potentially due to peer dependency being bumped to a major version of webpack, may require its own major version altering to suit. Will let maintainers be the judge of that
Other information