feat: migrate to ESLint v9 with flat configuration#430
Open
outslept wants to merge 2 commits intoeditorconfig:mainfrom
Open
feat: migrate to ESLint v9 with flat configuration#430outslept wants to merge 2 commits intoeditorconfig:mainfrom
outslept wants to merge 2 commits intoeditorconfig:mainfrom
Conversation
Transition from ESLint v8 to v9 using the new flat configuration format. Convert .eslintrc.json to eslint.config.js and incorporate .eslintignore paths directly into the configuration.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Please fill in this template.
tscw/o errors (same asnpm run build).npm run lintw/o errors. *Transition from ESLint v8 to v9 using the new flat configuration format. Convert .eslintrc.json to eslint.config.js and incorporate .eslintignore paths directly into the configuration.
Note: After migrating to ESLint 9, the linter reports 56 errors that weren't present with ESLint 8. This is likely due to changes in recommended rule sets or rule implementation in the new version.
The migration itself is working correctly (e.g. tools like this https://eslint.org/blog/2024/04/eslint-config-inspector/ are working fine), we need to decide how to handle these new linting errors before merging.
Coming from #406