chore: upgrade ESLint to v10#353
Merged
Merged
Conversation
eslint-plugin-import doesn't yet support ESLint 10. Imports in src/ don't use extensions and bundling is handled by tsup, so the import/extensions rule is no longer needed.
Add format/format:check scripts and a CI step that runs `prettier --check .` alongside the existing lint step. Reformat the four files that were drifting from the prettier config.
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
2 participants
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.
Summary
eslint9.39.4 → 10.4.0 and@eslint/js9.39.4 → 10.0.1eslint-plugin-importandeslint-import-resolver-typescriptsince they don't yet support ESLint 10, and the only rule in use (import/extensions) is unnecessary — imports insrc/don't use extensions and bundling is handled by tsupTest plan
npm run lintpassesnpm test— all 90 tests passGenerated by Claude Code