Re-add webpack-manifest-plugin dependency, which was previously embedded in #921
#1382
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Kocal
force-pushed
the
re-add-webpack-manifest-plugin-dependency
branch
from
b765b91 to
77de962
Compare
Kocal
force-pushed
the
re-add-webpack-manifest-plugin-dependency
branch
from
77de962 to
d5d6b7b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While working on #1381, I noticed that
lib/webpack-manifest-plugin/was https://github.com/shellscape/webpack-manifest-plugin embedded with fix shellscape/webpack-manifest-plugin#249The package was embedded because it was possible for the upstream PR to never be merged, but it has been merged and released.
We should not have any BCs from https://github.com/shellscape/webpack-manifest-plugin/releases