fix(utils): force get-matched-rule-4 to use nearest webpack installation #463
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.
What kind of change does this PR introduce? (bugfix, feature, docs update, improvement)
bugfix
What is the current behavior? (You can also link to an open issue here)
#461
What is the new behavior (if this is a feature change)?
The
get-matched-rule-4
util will now loadwebpack/lib/RuleSet
only from the nearestwebpack
installation, it will no longer look up the chain for additionalwebpack
installations until it finds theRuleSet
file.This eliminates the issue raised in #461, where the wrong version of
webpack
is loaded in a scenario where multiple nestedwebpack
installations exist.Does this PR introduce a breaking change?
No
Please check if the PR fulfills contributing guidelines