Repository navigation
chore(deps): upgrade to ESLint 10 - #42
Merged
Merged
Conversation
Assisted-by: Claude Opus 5.5
Assisted-by: Claude Opus 5.5
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.
Replaces #40: @eslint/js 10 requires eslint 10, so both move together (typescript-eslint and eslint-plugin-react-hooks already accept ESLint 10). The new recommended
preserve-caught-errorrule flagged onethrowinscripts/check-sigima-release.mjs, which now passes the original error ascause.Dependabot now groups
eslintand@eslint/*so their majors arrive in one PR, and ignores TypeScript majors: typescript-eslint 8.71 still caps its peer range at<6.1.0, so TypeScript 7 (#41) cannot resolve.ESLint, Prettier, Vitest (745) and
npm audit(0 vulnerabilities) pass locally.