nextjs - ✅(Solved) Fix ESLint config missing in next.config after upgrading to 16.0.0-beta.0 [1 pull requests, 4 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

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#84772Fetched 2026-04-08 02:18:30
View on GitHub
Comments
4
Participants
3
Timeline
14
Reactions
1
Assignees
Timeline (top)
commented ×4labeled ×2assigned ×1closed ×1

Fix Action

Fixed

PR fix notes

PR #84781: docs: getting started installation and next lint removal

Description (problem / solution / changelog)

  • verify rendering of the changes

Also addressing: #84772

Changed files

  • docs/01-app/01-getting-started/01-installation.mdx (modified, +13/-3)
  • docs/01-app/02-guides/migrating/from-create-react-app.mdx (modified, +1/-1)
  • docs/01-app/03-api-reference/05-config/01-next-config-js/eslint.mdx (removed, +0/-22)
  • docs/01-app/03-api-reference/05-config/02-typescript.mdx (modified, +1/-1)
  • docs/01-app/03-api-reference/05-config/03-eslint.mdx (modified, +184/-118)
  • docs/01-app/03-api-reference/06-cli/create-next-app.mdx (modified, +1/-3)
  • docs/01-app/03-api-reference/06-cli/next.mdx (modified, +8/-51)
  • docs/02-pages/04-api-reference/04-config/01-next-config-js/eslint.mdx (removed, +0/-7)

Code Example

import type { NextConfig } from 'next';

   const nextConfig: NextConfig = {
    // Object literal may only specify known properties, and 'eslint' does not exist in type 'NextConfig'.
     eslint: {
       ignoreDuringBuilds: true,
     },
   };

   export default nextConfig;

---

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.0.0: Wed Sep 17 21:38:03 PDT 2025; root:xnu-12377.1.9~141/RELEASE_ARM64_T8112
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 22.15.1
  npm: 10.9.4
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.0.0-beta.0 // Latest available version is detected (16.0.0-beta.0).
  eslint-config-next: 15.5.4
  react: 19.2.0
  react-dom: 19.2.0
  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/abhishekmardiya/nextconfig-eslint-reproduction

To Reproduce

Steps to Reproduce

Add an eslint field in next.config.js:

import type { NextConfig } from 'next';

const nextConfig: NextConfig = {
 // Object literal may only specify known properties, and 'eslint' does not exist in type 'NextConfig'.
  eslint: {
    ignoreDuringBuilds: true,
  },
};

export default nextConfig;

Current behavior

After upgrading to Next.js 16.0.0-beta.0, the eslint option is no longer available in next.config.js.

Expected behavior

eslint should still be a valid configuration field in next.config.js (or documentation should reflect its removal/change if this was intentional).

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.0.0: Wed Sep 17 21:38:03 PDT 2025; root:xnu-12377.1.9~141/RELEASE_ARM64_T8112
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 22.15.1
  npm: 10.9.4
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.0.0-beta.0 // Latest available version is detected (16.0.0-beta.0).
  eslint-config-next: 15.5.4
  react: 19.2.0
  react-dom: 19.2.0
  typescript: 5.9.3
Next.js Config:
  output: N/A

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

TypeScript

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

next dev (local)

Additional context

extent analysis

TL;DR

The eslint option is no longer available in next.config.js due to a change in the NextConfig type definition in Next.js 16.0.0-beta.0.

Guidance

  • Review the Next.js documentation to see if the eslint option has been officially removed or replaced.
  • Check the config-shared.ts file in the Next.js repository to understand the changes made to the NextConfig type definition.
  • Consider using a different configuration option or a custom solution to achieve the desired ESLint behavior.
  • Verify that the eslint-config-next package is compatible with Next.js 16.0.0-beta.0.

Example

No code snippet is provided as the issue is related to a type definition change.

Notes

The removal of the eslint option from the NextConfig type definition may indicate a intentional change in Next.js. It's essential to review the documentation and repository to understand the reasoning behind this change.

Recommendation

Apply workaround: The best course of action is to find an alternative configuration option or a custom solution to achieve the desired ESLint behavior, as the eslint option is no longer available in next.config.js.

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…

FAQ

Expected behavior

eslint should still be a valid configuration field in next.config.js (or documentation should reflect its removal/change if this was intentional).

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

nextjs - ✅(Solved) Fix ESLint config missing in next.config after upgrading to 16.0.0-beta.0 [1 pull requests, 4 comments, 3 participants]