Issue Station
Sign In
Tools hereToolbox

nextjs - ✅(Solved) Fix Add support for `eslint` `v10` in `eslint-config-next` [5 pull requests, 5 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#91702•Fetched 2026-04-08 01:02:24
View on GitHub
Comments
5
Participants
4
Timeline
25
Reactions
0
Author
pcaversacciopcaversaccio
Participants
github-actions[bot]github-actions[bot]icyJosephicyJosephnehaaprasadnehaaprasadpcaversacciopcaversaccio
Timeline (top)
cross-referenced ×11commented ×5labeled ×2subscribed ×2

Error Message

WARN  Issues with peer dependencies found

Fix Action

Fixed

PR fix notes

PR #91710: fix : add ESLint v10 support to eslint-config-next

Description (problem / solution / changelog)

Fixes #91702

What?

  • Switched to eslint-plugin-import-x.
  • Updated import rules/settings to import-x.
  • Updated lint plugin versions in eslint-config-next.

Why?

  • Reduce ESLint v10 peer dependency warnings.
  • Align with plugins that support ESLint v10.

How?

  • Edited packages/eslint-config-next/package.json.
  • Edited packages/eslint-config-next/src/index.ts.

Changed files

  • packages/eslint-config-next/package.json (modified, +2/-2)

Code Example

Progress: resolved 816, reused 730, downloaded 16, added 21, done
 WARN  Issues with peer dependencies found
interface
├─┬ eslint-plugin-import 2.32.0
│ └── ✕ unmet peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8 || ^9": found 10.0.3
└─┬ eslint-config-next 16.2.0
  ├─┬ eslint-plugin-import 2.32.0
  │ └── ✕ unmet peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8 || ^9": found 10.0.3
  ├─┬ eslint-plugin-react 7.37.5
  │ └── ✕ unmet peer eslint@"^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7": found 10.0.3
  ├─┬ eslint-plugin-react-hooks 7.0.1
  │ └── ✕ unmet peer eslint@"^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0-0 || ^9.0.0": found 10.0.3
  └─┬ eslint-plugin-jsx-a11y 6.10.2
    └── ✕ unmet peer eslint@"^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9": found 10.0.3

---

Operating System:
  Platform: linux
  Arch: x64
  Version: #31-Ubuntu SMP PREEMPT_DYNAMIC Tue Feb 20 15:10:00 UTC 2026
  Available memory (MB): 7845
  Available CPU cores: 8
Binaries:
  Node: 24.14.0
  npm: 11.9.0
  Yarn: N/A
  pnpm: 10.32.1
Relevant Packages:
  next: 16.2.0 // Latest available version is detected (16.2.0).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/pcaversaccio/createx

To Reproduce

  1. git clone https://github.com/pcaversaccio/createx.git
  2. cd interface
  3. ncu -u (ncu = https://www.npmjs.com/package/npm-check-updates)
  4. cd ..
  5. pnpm up -r

Current vs. Expected behavior

Current:

Progress: resolved 816, reused 730, downloaded 16, added 21, done
 WARN  Issues with peer dependencies found
interface
├─┬ eslint-plugin-import 2.32.0
│ └── ✕ unmet peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8 || ^9": found 10.0.3
└─┬ eslint-config-next 16.2.0
  ├─┬ eslint-plugin-import 2.32.0
  │ └── ✕ unmet peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8 || ^9": found 10.0.3
  ├─┬ eslint-plugin-react 7.37.5
  │ └── ✕ unmet peer eslint@"^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7": found 10.0.3
  ├─┬ eslint-plugin-react-hooks 7.0.1
  │ └── ✕ unmet peer eslint@"^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0-0 || ^9.0.0": found 10.0.3
  └─┬ eslint-plugin-jsx-a11y 6.10.2
    └── ✕ unmet peer eslint@"^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9": found 10.0.3

Expected: No peer dependency conflicts found.

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #31-Ubuntu SMP PREEMPT_DYNAMIC Tue Feb 20 15:10:00 UTC 2026
  Available memory (MB): 7845
  Available CPU cores: 8
Binaries:
  Node: 24.14.0
  npm: 11.9.0
  Yarn: N/A
  pnpm: 10.32.1
Relevant Packages:
  next: 16.2.0 // Latest available version is detected (16.2.0).
  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

extent analysis

Fix Plan

To resolve the peer dependency conflicts, we need to update the eslint version to a range that is compatible with the peer dependencies of eslint-plugin-import, eslint-config-next, eslint-plugin-react, eslint-plugin-react-hooks, and eslint-plugin-jsx-a11y.

Here are the steps to fix the issue:

  • Update eslint to version 9.34.0 which is the latest version that is compatible with the peer dependencies:
pnpm install [email protected] --save-dev
  • Alternatively, you can also use the --legacy-peer-deps flag with pnpm to ignore the peer dependency conflicts:
pnpm install --legacy-peer-deps

However, this approach is not recommended as it may lead to unexpected behavior or errors.

Verification

To verify that the fix worked, run the following command:

pnpm install

If there are no peer dependency conflicts, the installation should complete without any warnings.

Extra Tips

  • Make sure to update the eslint version in your package.json file to ensure that the fix is persisted.
  • If you are using a pnpm version older than 7.0.0, you may need to use the --force flag instead of --legacy-peer-deps.
  • It's recommended to use a consistent version of eslint across all dependencies to avoid peer dependency conflicts.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#tensor shape#agent execution#callback error#memory management#API rate limit#dependency conflict

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING