Migrate to ESLint flat config & neostandard #2142
Open
+962
−798
Conversation
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
MetRonnie
added
dependencies
MetRonnie
commented
Apr 15, 2025
Comment on lines
+91
to
+94
| plugins: { | ||
| cypress: pluginCypress, | ||
| }, | ||
| extends: ['cypress/recommended'], |
There was a problem hiding this comment.
I found eslint/eslint#19116 more illuminating than anything in the ESLint docs!
MetRonnie
force-pushed
the
major-eslint
branch
2 times, most recently
from
2c918b3 to
920a918
Compare
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.
Supersedes #1747
The flat config format in ESLint 9 in some ways makes more sense than the old format, but the documentation is rather lacking. Essentially, you've got an array of configuration objects, that ESLint combines.
I have moved from standard to neostandard, as standard is apparently not maintained anymore. Unfortunately, neostandard's documentation is also rather lacking. It aims to replace the need for a normal ESLint config, except that only seems to work for very simple use cases. But it can stil be combined with a normal flat ESLint config. Several of the ESLint plugins we use are bundled with neostandard, so I've removed them from our dependencies.
Check List
CONTRIBUTING.mdand added my name as a Code Contributor.