fix(utils): Account for rule property "generator"#454
Merged
d3x42 merged 1 commit intoJetBrains:masterfrom May 6, 2021
ihmels:patch-1
Merged
fix(utils): Account for rule property "generator"#454d3x42 merged 1 commit intoJetBrains:masterfrom ihmels:patch-1
d3x42 merged 1 commit intoJetBrains:masterfrom
ihmels:patch-1
Conversation
In Webpack 5 a new property "generator" has been added to the rule definition, which must be accounted for in the rule set. Fixes #428. (See vuejs/vue-loader#1753)
|
When will there be a new version? I need this PullRequest urgently. |
Contributor
|
svg-sprite-loader@6.0.7 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
In Webpack 5 a new property "generator" has been added to the rule definition, which must be accounted for in the rule set.
What kind of change does this PR introduce?
Bugfix (See vuejs/vue-loader#1753)
What is the current behavior?
#428
Does this PR introduce a breaking change?
No