[ESLint v10]: TypeError: contextOrFilename.getFilename is not a function when running ESLint v10

[bennajah]

Link to the code that reproduces this issue

https://github.com/bennajah/nextjs16

To Reproduce

1. Create a next.js project or clone this repo
2. Upgrade eslint to v10 .
3. Run eslint

Current vs. Expected behavior

After upgrading ESLint to v10 in a Next.js project, running bun eslint causes the following error:

PS C:\Users\benna\dev\my-app> bun lint
$ eslint

Oops! Something went wrong! :(

ESLint: 10.0.0

TypeError: Error while loading rule 'react/display-name': contextOrFilename.getFilename is not a function
Occurred while linting C:\Users\benna\dev\my-app\app\layout.tsx
    at resolveBasedir (C:\Users\benna\dev\my-app\node_modules\eslint-plugin-react\lib\util\version.js:31:100)
    at detectReactVersion (C:\Users\benna\dev\my-app\node_modules\eslint-plugin-react\lib\util\version.js:85:19)
    at getReactVersionFromContext (C:\Users\benna\dev\my-app\node_modules\eslint-plugin-react\lib\util\version.js:116:25)
    at testReactVersion (C:\Users\benna\dev\my-app\node_modules\eslint-plugin-react\lib\util\version.js:181:28)
    at usedPropTypesInstructions (C:\Users\benna\dev\my-app\node_modules\eslint-plugin-react\lib\util\usedPropTypes.js:307:36)
    at Components.componentRule (C:\Users\benna\dev\my-app\node_modules\eslint-plugin-react\lib\util\Components.js:940:37)
    at createRuleListeners (C:\Users\benna\dev\my-app\node_modules\eslint\lib\linter\linter.js:497:15)
    at C:\Users\benna\dev\my-app\node_modules\eslint\lib\linter\linter.js:623:7
    at Array.forEach (<anonymous>)
    at runRules (C:\Users\benna\dev\my-app\node_modules\eslint\lib\linter\linter.js:557:31)

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 12244
  Available CPU cores: 8
Binaries:
  Node: 24.13.0
  npm: 11.6.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.1.6 // Latest available version is detected (16.1.6).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Linting

Which stage(s) are affected? (Select all that apply)

Other (Deployed)

Additional context

No response

[simonhudson]

Also seeing same error for react/no-direct-mutation-state rule when running Lint in GH actions

[jWytrzes]

Same here and also same with react/no-direct-mutation-state as mentioned

EDIT: And when I turn off both of them it changes to react/no-render-return-value, so probably it can go on like that

[OscarGauss]

Temporary Fix for ESLint v10:
This error happens because eslint-plugin-react (a dependency of eslint-config-next) uses the legacy context.getFilename() API for version auto-detection, which was removed in ESLint v10.
To fix this, you must explicitly define your React version in your eslint.config.mjs settings to bypass the auto-detection logic.
I've created a Gist with the corrected configuration for Next.js + ESLint 10: "Next.js ESLint v10 Fix"
Key change:

{
  settings: {
    react: { version: "19" } // Avoids auto-detection crash
  }
}