Update loader-utils dependency #1
Open
Conversation
This file contains 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
The original package.json depends on "loader-utils" version 0.2.x. But the last version of this series (0.2.17) emits an annoying warning for every webpack build: > DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see webpack/loader-utils#56 > parseQuery() will be replaced with getOptions() in the next major version of loader-utils. Instead of updating this dependency to a major new version (which may require code changes), this quick-fix simply locks the dependency to 0.2.16, which is the last-but-one of the series, and which does not emit that warning.
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.
The original package.json depends on "loader-utils" version 0.2.x.
But the last version of this series (0.2.17) emits an annoying warning for every webpack build:
Instead of updating this dependency to a major new version (which may require code changes),
this quick-fix simply locks the dependency to 0.2.16, which is the last-but-one of the series,
and which does not emit that warning.