build: upgrade typescript-eslint to v8 - #3417
Open
aresnik11 wants to merge 5 commits into
Open
Conversation
typescript-eslint 5.62 -> 8.43.0 (plugin/parser/utils, + rule-tester) and @codecademy/eslint-config 8.0.0 -> 8.2.0, so TS 5.9 is officially supported and the version warning on `yarn lint` goes away. Pinned to 8.43.0 to match mono. Also add import/jest/unused-imports at the root so the shared config's plugins resolve (they no longer hoist under the newer config). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- RuleTester moved to @typescript-eslint/rule-tester with flat-config languageOptions (v8 dropped ESLintUtils.RuleTester and the string parser) - Use nodenext resolution in tsconfig.spec.json so the rule-tester exports subpaths resolve (still emits CommonJS for ts-jest) - Drop docs.recommended from rule meta (removed from RuleMetaDataDocs in v8) - Compare node types against AST_NODE_TYPES to satisfy no-unsafe-enum-comparison - Remove a duplicate valid test case (v8 RuleTester now rejects duplicates) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Disable no-empty-object-type / no-wrapper-object-types (v8 successors of
ban-types / no-empty-interface, which the shared config already disables;
mono disables no-empty-object-type too)
- Disable no-base-to-string: flags long-standing ReactNode->string aria/id
coercions; hardening those is a separate a11y effort
- Allow `== null` / `!= null` via eqeqeq { null: 'ignore' }
- For *.mdx, turn off import/namespace and no-unused-expressions, which
misfire on MDX imports and inline prose expressions
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
View your CI Pipeline Execution ↗ for commit bd9abf7 ☁️ Nx Cloud last updated this comment at |
|
- Add missing React keys in styleguide list/story maps (jsx-key) - Preserve the full ButtonTypes union and disable no-duplicate-type-constituents there: the five button components are structurally identical, but the union intentionally enumerates them all - Drop a genuinely redundant `| undefined` on an optional param and a duplicate literal union member (autofix); prefer optional chaining - Disable import/namespace on a dynamic namespace key access it can't statically validate - Collapse multi-line JSX string attributes in two MDX files that crashed the eslint-mdx v3 parser - Import-sort fixes Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
aresnik11
force-pushed
the
ajr-bump-typescript-eslint
branch
from
August 19, 2026 15:25
bd9abf7 to
cb87024
Compare
aresnik11
commented
Aug 19, 2026
| | 'search' | ||
| | 'month' | ||
| | 'tel' | ||
| | 'time' |
Contributor
Author
There was a problem hiding this comment.
duplicate, also listed above on line 336
aresnik11
commented
Aug 19, 2026
| `import defaultImport from 'fileName.json'`, | ||
| `import defaultImport from 'fileName.md'`, | ||
| `import defaultImport from 'fileName.mdx'`, | ||
| `import defaultImport from 'fileName.svg'`, |
Contributor
Author
There was a problem hiding this comment.
duplicate. same thing on line 19
Collaborator
|
📬 Published Alpha Packages:
|
Contributor
|
🚀 Styleguide deploy preview ready! Preview URL: https://6a85ce00e3468583f5c983bc--gamut-preview.netlify.app |
aresnik11
marked this pull request as ready for review
August 19, 2026 18:39
dreamwasp
reviewed
Aug 19, 2026
dreamwasp
left a comment
Contributor
There was a problem hiding this comment.
lgt, would just like to test eslint-plugin-gamut in mono to make sure it still works there
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
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.
Overview
Upgrades
typescript-eslintfrom v5 to v8 so the current TypeScript version (5.9.3) is officially supported andyarn lintno longer prints the "TypeScript version not officially supported by @typescript-eslint" warning.Root cause:
@typescript-eslint@5.62supports TS<5.2, but the repo is on TS5.9.3. Moving to v8 (via@codecademy/eslint-config8.0.0 → 8.2.0, which already uses@typescript-eslint@^8.31) resolves it. Pinned to 8.43.0 exact to matchmono. No ESLint or Node upgrade needed — v8 peerseslint ^8.57(repo is on 8.57.1) and Node>=18.18(repo is on 22).Commits
@typescript-eslint/*5.62 → 8.43.0 (plugin, parser, utils, + newrule-tester),@codecademy/eslint-config→ 8.2.0. Addedeslint-plugin-import/-jest/-unused-importsat the root so the shared config's plugins resolve (they no longer hoist under the newer config).RuleTestermoved to@typescript-eslint/rule-testerwith flat-configlanguageOptions;nodenextresolution intsconfig.spec.json; removeddocs.recommendedfrom rule meta;AST_NODE_TYPEScomparisons; removed a duplicate test case..eslintrc.js(see below).Rule-config decisions
Bumping the config pulled newer plugin versions, surfacing 139 new lint errors. Handled as:
mono+ the config's existingban-types/no-empty-interfaceintent):@typescript-eslint/no-empty-object-type(98 hits —monodisables this too)@typescript-eslint/no-wrapper-object-types(5)@typescript-eslint/no-base-to-string(5 — flags long-standingReactNode → stringaria/id coercions; hardening those is a separate a11y effort, noted in a code comment)eqeqeq: the 2 hits were idiomatic== null/!= nullnullish checks → allowed viaeqeqeq: ['error', 'always', { null: 'ignore' }](still enforces===everywhere else).*.mdx: turned offimport/namespaceand@typescript-eslint/no-unused-expressions, which misfire on MDX imports and inline prose expressions like{'>'}.react/jsx-key, 3no-unsafe-enum-comparison, 2no-unused-vars, plus autofixed dedupe / import-sort / optional-chaining.eslint-mdxnoteThe config bump also moves
eslint-mdx1.x → 3.x. The v3 parser crashed on two docs files (assert.ok(code[lastAttrOffset] === attrQuote)) — caused by multi-line JSX string attributes (<Callout text="line one\n line two" />). Fixed by collapsing those to single-line attributes. No functional change to the docs.PR Checklist
Testing Instructions
Expected:
yarn lintexits 0 with no version warning;eslint-plugin-gamuttests (45) and build pass; typescript-eslint resolves to 8.43.0.PR Links and Envs