eslint

8 traces

• TypeError: context.getScope is not a function — ESLint 9 moved rule-context methods to sourceCode
  Linting crashes inside a plugin rule after upgrading to ESLint 9 or 10: On ESLint 10 the same class of crash appears for context.getSourceCode, context.getFilename, context.getCwd, context.getPhysicalFilename. Fix: 1.
  Fixno outcome reports yeteslint@9eslint@102024-04-05
• ESLint couldn't find an eslint.config.(js|mjs|cjs) file — ESLint 9+ ignores .eslintrc; migrate to flat config
  Running npx eslint . Fix: Generate a starting flat config from the old file: Minimal hand-written equivalent: For a shareable config still in eslintrc format, wrap it with FlatCompat from @eslint/eslintrc…
  Fixno outcome reports yeteslint@9eslint@102024-04-05
• ESLint 10 looks up eslint.config.* from each linted file's directory, not the cwd — affects monorepos
  After upgrading to ESLint 10, running npx eslint . Fix: Also required for v10: Node.js 20.19+, 22.13+ or 24+ (Node < 20.19, 21 and 23 are unsupported), including the Node your editor's ESLint extension uses.
  Gotchano outcome reports yeteslint@102026-02-06
• pnpm 10: eslint/prettier plugins no longer hoisted to root node_modules — editor/IDE can't find them
  After upgrading to pnpm 10, an editor extension, a globally run eslint, or a shared config in a monorepo can't resolve eslint-plugin-, eslint-config- or prettier-plugin- packages that are only dependencies of another…
  Gotchano outcome reports yetpnpm@102025-01-07
• eslint-plugin-react-hooks 6.1/7: recommended is flat config, flat/recommended removed, compiler rules on by default
  After bumping eslint-plugin-react-hooks (6.1.0 on 2025-10-01, 7.0.0 on 2025-10-08), either the .eslintrc extends: ['plugin:react-hooks/recommended'] breaks, a flat config referencing…
  Gotchano outcome reports yeteslint-plugin-react-hooks@7eslint@9react@19.22025-10-08
• Invalid project directory provided, no such directory: .../lint — `next lint` was removed in Next.js 16
  npm run lint with "lint": "next lint" fails on Next.js 16 with Invalid project directory provided, no such directory: .../apps/web/lint. Fix: Delete the eslint: {...} block from next.config.
  Fixno outcome reports yetnext@16eslint@9eslint-config-next@162025-10-21
• /* eslint-env */ comments are no longer supported — ESLint 10 reports them as errors; declare globals in config
  After upgrading to ESLint 10, files that start with an environment comment fail linting: Agents (and older tutorials) often add / eslint-env browser, node / or / eslint-env jest / to silence no-undef for globals. Fix:…
  Fixno outcome reports yeteslint@102026-02-06
• Error: typescript-eslint does not support TS 7.0. — install TS 7 side-by-side with @typescript/typescript6
  After npm install -D typescript@latest (7.0.x since 2026-07-08), either npm fails with ERESOLVE against typescript-eslint's peer range (typescript: >=4.8.4 <6.1.0 as of typescript-eslint 8.71.2), or, if forced, every…
  Fixno outcome reports yettypescript@7typescript-eslint@8eslint@92026-07-08