feat: move to ESLint v9 👏#250
Merged
Merged
Conversation
BREAKING CHANGE: Projects must now use ESLint v9 in order to use these rulesets.
robertrossmann
requested review from
developer239 and
matejpolak
as code owners
robertrossmann
added
enhancement
- @strv/eslint-config-base@5.0.0-alpha.0 - @strv/eslint-config-graphql@3.0.0-alpha.0 - @strv/eslint-config-mocha@5.0.0-alpha.0 - @strv/eslint-config-node@5.0.0-alpha.0 - @strv/eslint-config-react@6.0.0-alpha.0 - @strv/eslint-config-typescript@6.0.0-alpha.0
- @strv/eslint-config-typescript@6.0.0-alpha.1
- @strv/eslint-config-base@5.0.0-alpha.1 - @strv/eslint-config-graphql@3.0.0-alpha.1 - @strv/eslint-config-mocha@5.0.0-alpha.1 - @strv/eslint-config-node@5.0.0-alpha.1 - @strv/eslint-config-react@6.0.0-alpha.1 - @strv/eslint-config-typescript@6.0.0-alpha.2
Used when working with vitest.
jirikapoun
reviewed
Feb 19, 2025
jirikapoun
left a comment
jirikapoun
left a comment
Contributor
There was a problem hiding this comment.
I have added one small suggestion, otherwise it looks good.
I have tried out the new version in the Surge codebase and only a few adjustments were necessary:
- Rename
@typescript-eslint/indentrule config to@stylistic/indent - Rename
@typescript-eslint/no-throw-literalrule config to@typescript-eslint/only-throw-error - Add ignore for
fetchandFormDatatonode/no-unsupported-features/node-builtinsrule config (or potentially even better, upgrade to Node 22)
I also had to regenerate package-lock.json in order to resolve all peer deps conflicts and completely drop one very old ESLint plugin (eslint-plugin-filenames) – I think it would be possible to salvage it by patching it, but we don't really need it so I didn't bother.
Co-authored-by: jirikapoun <jirikapoun@jirikapoun.cz>
robertrossmann
force-pushed
the
feat/eslint/v9-support
branch
from
d9e8ce1 to
517cc33
Compare
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.
BREAKING CHANGE: Projects must now use ESLint v9 in order to use these rulesets.