chore: bump ESLint to v8.57.0 #3735
Merged
+144
−374
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
david-gomes5
changed the title
david-gomes5
force-pushed
the
chore/bump-eslint-to-v8.52.0
branch
from
b63ce81
to
e51c44a
Compare
DeadEnglish
approved these changes
May 14, 2024
|
🎉 This PR is included in version 9.4.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
What does this do?
Not bumped to v9 since we're waiting for typescript ESLint to fully release v8 that supports ESLint v9:
typescript-eslint/typescript-eslint#8211 (comment)
Breaking changes
tl;dr*: Interest is mostly around the rule changes, worse case scenario, we get additional linting errors. We already use the latest LTS Node version across the org (v20)
*: too long, didn't read