Upgrade to ESLint 10 once the eslint-config-next plugins support it

Aperta
  • Qualcosa non va?
#277 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
35/100
Tipo di issue
Refactoring
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
eslint, nextjs, node.js, react, typescript
Ambito
build-system, developer-experience

Direzione di ricerca

Start from the eslint pin in package.json and check whether the current eslint-config-next release still lists the same peer ranges for eslint-plugin-react, eslint-plugin-import and eslint-plugin-jsx-a11y (inspect with npm ls eslint and the plugins' package.json files). If the peers now accept ^10, bump to ^10 on its own branch, read the ESLint 10 migration guide, and run npm run lint. Done looks like a clean npm ci with no ERESOLVE overrides and a passing lint run. Note the maintainer decided on 2026-11-10 to wait, so confirm upstream support before starting.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: ci blocked enhancement priority: P3 size: S

Problem

npm ci warns that [email protected] is no longer supported:

npm warn deprecated [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.

The latest major is ESLint 10 (10.14.0, dist-tag latest; 9.39.5 is the maintenance tag). package.json pins "eslint": "^9".

Why it is blocked

[email protected] (latest 16.4.6) brings in three plugins whose newest releases do not declare ESLint 10 as a supported peer:

Plugin Latest Peer eslint range
eslint-plugin-react 7.37.5 ^3 || ... || ^9.7
eslint-plugin-import 2.32.0 ^2 || ... || ^9
eslint-plugin-jsx-a11y 6.10.2 ^3 || ... || ^9

Already compatible: [email protected] and [email protected] both list ^10.

What a forced upgrade did (throwaway worktree, 2026-11-10)

  • npm install -D eslint@^10 installed 10.14.0 with three ERESOLVE overriding peer dependency warnings, and npm ls reported the peers as invalid.
  • npm run lint exited 0.
  • A probe file got the same 5 findings under 9.39.5 and 10.14.0: react-hooks/rules-of-hooks, react/jsx-key, @next/next/no-img-element, jsx-a11y/alt-text, import/no-anonymous-default-export.

So it runs today, but outside the ranges the plugins support, and it swaps one warning for three. Decision on 2026-11-10: stay on ESLint 9 until the plugins support 10.

Unblock when

eslint-config-next ships a release where every bundled plugin declares ESLint 10 in its peer range (or drops the plugin). Then bump eslint to ^10 in its own branch, read the ESLint 10 migration guide, and run npm run lint.

Model: anthropic/claude-opus-5-5 | Reasoning effort: high

Lingua principale
TypeScript
Stelle
1
Fork
1
Merge medio
6h 56m
PR unite (30g)
136

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di eddiejaoude/StackDash

Tutte le issue di eddiejaoude/StackDash

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.