Upgrade to ESLint 9, flatconfig and Node.js 18 (#173) #175
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
Upgrade the eslint dependency. Change the documentation and tests to use the new configuration format. Also, upgrade Node.js in the build pipeline. > When ESLint v10.0.0 is released (end of 2024 or early 2025 in all likelihood), the eslintrc configuration system will be completely removed. https://eslint.org/blog/2023/10/flat-config-rollout-plans/#eslintrc-removed-in-eslint-v10.0.0 * Describe and test the usage only with flatconfig. It'll be the only config format soon. Who needs to retain `.eslintrc` can stay with eslint 8. * ESLint 9 supports only Node.js `^18.18.0 || ^20.9.0 || >=21.1.0`. * The formatter `eslint-tap` works, but because it doesn't follow the NPM package naming convention `eslint-formatter-*`, it has to be specified using a path to the script with the main exports.
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.
Upgrade the eslint dependency. Change the documentation and tests to use the new configuration format. Also, upgrade Node.js in the build pipeline.
https://eslint.org/blog/2023/10/flat-config-rollout-plans/#eslintrc-removed-in-eslint-v10.0.0
.eslintrccan stay with eslint 8.^18.18.0 || ^20.9.0 || >=21.1.0.eslint-tapworks, but because it doesn't follow the NPM package naming conventioneslint-formatter-*, it has to be specified using a path to the script with the main exports.Fixes #173