Use correct standard
peer dependencies
#27425
Closed
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.
Why:
dependabot can not help with updating from unmaintained modules to maintained forks, that needs manual intervention. This replaces the unmaintained (and for
eslint-config-standard
incorrect)eslint-plugin-node
with theeslint-plugin-n
fork that's maintained by the official ESLint Community org.What's being changed (if available, include any code snippets, screenshots, or gifs):
Replace
eslint-plugin-node
with the now used official forkeslint-plugin-n
.Also update to latest version of
eslint-config-standard
and its peer dependencies.Since it can be hard for users of
eslint-plugin-node
to find out that there's a maintained fork from the official ESLint Community project I'm doing a drive where I'm making PR:s to some projects to raise awareness.See: eslint-community/eslint-plugin-n#100
Disclaimer: I'm a co-maintainer of both
standard
andeslint-plugin-n
Check off the following:
Not applicable for this
I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in thedata
directory.For content changes, I have completed the self-review checklist.