specify eslint-plugin-n@^16.0.0 as valid peer dependency
#64
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
|
🙌 Thanks for opening this pull request! You're awesome. |
|
Updated dependencies detected. Learn more about Socket for GitHub ↗︎
|
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.
Renovate cannot update
eslint-plugin-nin my NPM projects to v16 becauseeslint-config-semistandarddoes not see it as a valid peer dependency:Since
eslint-config-semistandarddoes not directly make use ofeslint-plugin-n, but rather inherits the usage fromeslint-plugin-standard, this PR proposes to bump the peer dependency version range foreslint-plugin-nto match that ofeslint-plugin-standard@17.1.0.(Interesting that dependabot isn't trying to perform this major upgrade...)