Drop support below ESLint v8 #582
Merged
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
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.
Technically, ESLint v8 is end-of-life: https://eslint.org/blog/2024/09/eslint-v8-eol-version-support/
However, a lot of users will be stuck on ESLint v8 for a while, as noted by the npm download numbers https://www.npmjs.com/package/eslint?activeTab=versions, given the larger changes needed to migrate to flat config, so it doesn't hurt for us to continue to support the final version of ESLint v8.
Theoretically, dropping support for old versions of ESLint could make development easier for us. However, we haven't identified tangible examples of this yet. So we can be flexible on this as needed.