chore(deps): update dependency eslint to v10 #1571

claude · 2026-02-07T02:07:06Z

⚠️ Breaking Change: ESLint 10 Incompatibility

This upgrade to ESLint 10.0.0 introduces a critical compatibility issue:

Problem: eslint-plugin-react@7.37.5 (transitive dependency from eslint-config-next@16.1.6) is not compatible with ESLint 10.0.0.

Error:

TypeError: Error while loading rule 'react/display-name': contextOrFilename.getFilename is not a function

Why it happens: ESLint 10 changed the context API, and eslint-plugin-react@7.37.5 was only tested up to ESLint 9.7.

Recommendation: Do not merge this PR. Instead:

Wait for eslint-config-next to release a version compatible with ESLint 10, OR

Pin ESLint to ^9.39.2 and block ESLint 10 upgrades in Renovate config until ecosystem support catches up

See full review for detailed analysis and options →

claude · 2026-02-08T05:19:05Z

⚠️ Breaking Change: ESLint 10 Incompatibility

This upgrade introduces a critical compatibility issue:

Problem: eslint-plugin-react@7.37.5 (transitive dependency from eslint-config-next@16.1.6) does not support ESLint 10.

Error:

TypeError: Error while loading rule 'react/display-name': contextOrFilename.getFilename is not a function

Why: ESLint 10 changed the context API. eslint-plugin-react@7.37.5 only supports eslint ^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7.

Recommendation: Keep ESLint at ^9.39.2 until Next.js releases an ESLint 10-compatible version of eslint-config-next.

claude · 2026-02-08T06:26:15Z

⚠️ Breaking Change: ESLint 10 Incompatibility

This upgrade introduces a critical compatibility issue:

Problem: eslint-plugin-react@7.37.5 (transitive dependency from eslint-config-next@16.1.6) does not support ESLint 10.

Error:

TypeError: Error while loading rule 'react/display-name': contextOrFilename.getFilename is not a function

Why: ESLint 10 changed the context API. eslint-plugin-react@7.37.5 only supports eslint ^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7.

Recommendation: Keep ESLint at ^9.39.2 until Next.js releases an ESLint 10-compatible version of eslint-config-next.

claude · 2026-02-09T06:09:02Z

⚠️ Critical Breaking Change: ESLint 10 Incompatibility

This upgrade to ESLint 10.0.0 introduces a critical compatibility issue:

Problem: eslint-plugin-react@7.37.5 (transitive dependency from eslint-config-next@16.1.6) does not support ESLint 10.

Error from CI:

TypeError: Error while loading rule 'react/display-name': contextOrFilename.getFilename is not a function

Why: ESLint 10 changed the context API. eslint-plugin-react@7.37.5 only supports:

eslint: ^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7

Impact:

❌ Linting completely broken

❌ CI/CD pipeline fails

❌ Pre-commit hooks fail

❌ Cannot enforce code quality standards

Recommendation:

Keep ESLint at ^9.39.2 and configure Renovate to block ESLint 10 upgrades until the ecosystem catches up:

{ "packageRules": [ { "matchPackageNames": ["eslint"], "allowedVersions": "< 10" } ] }

Monitor for updates to either:

eslint-plugin-react v8.x (with ESLint 10 support)

eslint-config-next v16.2+ (with updated dependencies)

Expected timeline: Late February 2026

claude · 2026-02-09T10:44:04Z

🚨 Critical Breaking Change: ESLint 10 Incompatibility

This upgrade to ESLint 10.0.0 introduces a critical compatibility issue:

Problem: eslint-plugin-react@7.37.5 (transitive dependency from eslint-config-next@16.1.6) does not support ESLint 10.

Error from CI:

TypeError: Error while loading rule 'react/display-name': contextOrFilename.getFilename is not a function

Why: ESLint 10 changed the context API. eslint-plugin-react@7.37.5 only supports:

eslint: ^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7

Impact:

❌ Linting completely broken

❌ CI/CD pipeline fails

❌ Pre-commit hooks fail

❌ Cannot enforce code quality standards

Recommendation:

Keep ESLint at ^9.39.2 and configure Renovate to block ESLint 10 upgrades until the ecosystem catches up:

{ "packageRules": [ { "matchPackageNames": ["eslint"], "allowedVersions": "< 10" } ] }

Monitor for updates to either:

eslint-plugin-react v8.x (with ESLint 10 support)

eslint-config-next v16.2+ (with updated dependencies)

Expected timeline: Late February 2026

claude · 2026-02-09T20:32:08Z

🚨 Critical Breaking Change: ESLint 10 Incompatibility

This upgrade to ESLint 10.0.0 introduces a critical compatibility issue:

Problem: eslint-plugin-react@7.37.5 (transitive dependency from eslint-config-next@16.1.6) does not support ESLint 10.

Error from CI:

TypeError: Error while loading rule 'react/display-name': contextOrFilename.getFilename is not a function

Why: ESLint 10 changed the context API. eslint-plugin-react@7.37.5 only supports:

eslint: ^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7

Impact:

❌ Linting completely broken

❌ CI/CD pipeline fails

❌ Pre-commit hooks fail

❌ Cannot enforce code quality standards

Recommendation:

Keep ESLint at ^9.39.2 and configure Renovate to block ESLint 10 upgrades until the ecosystem catches up:

{ packageRules: [ { matchPackageNames: ["eslint"], allowedVersions: "<10", description: "eslint-plugin-react doesn't support ESLint 10 yet" } ] }

Monitor for updates to either:

eslint-plugin-react v8.x (with ESLint 10 support)

eslint-config-next v16.2+ (with updated dependencies)

Expected timeline: Late February 2026

claude · 2026-02-10T03:38:19Z

🚨 BREAKING: ESLint 10 Incompatibility

Critical Issue: This version upgrade breaks linting completely.

Error:

TypeError: Error while loading rule 'react/display-name': contextOrFilename.getFilename is not a function

Root Cause: eslint-plugin-react@7.37.5 (from eslint-config-next@16.1.6) only supports ESLint ≤9.7.

Required Action: Keep ESLint at ^9.39.2 until:

eslint-plugin-react@8.x releases with ESLint 10 support, OR

eslint-config-next@16.2+ updates to compatible plugins

Block in Renovate:

{ "packageRules": [{ "matchPackageNames": ["eslint"], "allowedVersions": "<10" }] }

Expected Timeline: March-April 2026

claude · 2026-02-10T12:58:25Z

🚨 CRITICAL: ESLint 10 Breaking Change

This upgrade breaks linting completely. The CI failure confirms the incompatibility issue.

Error from CI

TypeError: Error while loading rule 'react/display-name': contextOrFilename.getFilename is not a function

Root Cause

Package: eslint-plugin-react@7.37.5 (transitive dependency from eslint-config-next@16.1.6)

Peer dependency constraint: ^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7 (see pnpm-lock.yaml:1699)

Problem: ESLint 10 changed the context API, and eslint-plugin-react@7.37.5 was never tested with ESLint 10

Impact Assessment

❌ Linting: Completely broken - cannot run ESLint at all

❌ CI/CD: Build pipeline fails at lint step

❌ Pre-commit hooks: Will fail, blocking local commits

❌ Code quality: Cannot enforce any linting rules

Recommendation: DO NOT MERGE

This PR should remain blocked until the Next.js ecosystem adds ESLint 10 support.

Action items:

Block this upgrade in Renovate by adding to renovate.json:

{ "packageRules": [ { "matchPackageNames": ["eslint"], "allowedVersions": "<10", "description": "Block ESLint 10 until eslint-plugin-react@8.x is released" } ] }

Monitor for these releases:

eslint-plugin-react@8.x with ESLint 10 support (tracking issue)

eslint-config-next@16.2+ with updated dependencies

Expected timeline: March-April 2026 based on typical Next.js ecosystem update cycles

Why Not Workaround?

Cannot override transitive dependencies from eslint-config-next without breaking Next.js's own linting rules

Removing eslint-config-next would lose valuable Next.js-specific lint rules

This is a systemic ecosystem issue that requires upstream fixes

claude · 2026-02-10T20:12:11Z

🚨 BLOCKING: ESLint 10 Breaking Change

This version upgrade breaks linting completely due to an incompatible transitive dependency.

Error:

TypeError: Error while loading rule 'react/display-name': contextOrFilename.getFilename is not a function

Root Cause:

eslint-plugin-react@7.37.5 (from eslint-config-next@16.1.6) only supports eslint ^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7

ESLint 10 changed the context API, breaking compatibility

Impact:

❌ Linting completely broken

❌ CI/CD pipeline fails

❌ Pre-commit hooks fail

⚠️ Security rules not enforceable

Recommendation:

Keep ESLint at ^9.39.2 until the Next.js ecosystem adds ESLint 10 support.

Block in Renovate:

{ "packageRules": [{ "matchPackageNames": ["eslint"], "allowedVersions": "<10", "description": "Block ESLint 10 until eslint-plugin-react@8.x is released" }] }

Expected Timeline: March-April 2026

Tracking:

eslint-plugin-react ESLint 10 support

Wait for eslint-plugin-react@8.x or eslint-config-next@16.2+

claude · 2026-02-11T10:30:41Z

🚨 BLOCKING: ESLint 10 Breaking Change

This version upgrade breaks linting completely due to an incompatible transitive dependency.

Error:

TypeError: Error while loading rule 'react/display-name': contextOrFilename.getFilename is not a function

Root Cause:

eslint-plugin-react@7.37.5 (from eslint-config-next@16.1.6) only supports eslint ^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7 (see pnpm-lock.yaml:1699)

ESLint 10 changed the context API, breaking compatibility

Impact:

❌ Linting completely broken

❌ CI/CD pipeline fails

❌ Pre-commit hooks fail

⚠️ Security rules not enforceable

Recommendation:

Keep ESLint at ^9.39.2 until the Next.js ecosystem adds ESLint 10 support.

Block in Renovate:

{ "packageRules": [{ "matchPackageNames": ["eslint"], "allowedVersions": "<10", "description": "Block ESLint 10 until eslint-plugin-react@8.x is released" }] }

Expected Timeline: March-April 2026

Tracking:

eslint-plugin-react ESLint 10 support

Wait for eslint-plugin-react@8.x or eslint-config-next@16.2+

claude · 2026-02-11T17:16:51Z

🚨 BLOCKING: Incompatible Transitive Dependency

This ESLint upgrade breaks linting completely due to eslint-plugin-react@7.37.5 (from eslint-config-next@16.1.6).

Error:

TypeError: Error while loading rule 'react/display-name': contextOrFilename.getFilename is not a function

Root Cause:

eslint-plugin-react@7.37.5 peer dependency: ^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7

ESLint 10 changed context API (getFilename() → filename property)

Recommendation:
Block ESLint 10 in Renovate config until eslint-plugin-react@8.x or eslint-config-next@16.2+ releases with ESLint 10 support.

claude · 2026-02-11T21:52:24Z

🚨 BLOCKING: Incompatible Transitive Dependency

This ESLint upgrade breaks linting completely due to eslint-plugin-react@7.37.5 (from eslint-config-next@16.1.6).

Error:

TypeError: Error while loading rule 'react/display-name': contextOrFilename.getFilename is not a function

Root Cause:

eslint-plugin-react@7.37.5 peer dependency: ^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7 (see pnpm-lock.yaml:1699)

ESLint 10 changed context API (getFilename() → filename property)

Recommendation:
Block ESLint 10 in Renovate config until eslint-plugin-react@8.x or eslint-config-next@16.2+ releases with ESLint 10 support.

claude · 2026-02-14T02:17:20Z

🚨 BLOCKING: ESLint 10 Incompatibility

This version upgrade breaks linting completely due to an incompatible transitive dependency.

Error:

TypeError: Error while loading rule 'react/display-name': contextOrFilename.getFilename is not a function

Root Cause:

eslint-plugin-react@7.37.5 (from eslint-config-next@16.1.6) only supports eslint ^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7 (see pnpm-lock.yaml:1699)

ESLint 10 changed the context API (getFilename() method → filename property)

Impact:

❌ Linting completely broken (CI fails at lint step)

❌ Pre-commit hooks fail

❌ Code quality standards not enforceable

⚠️ Security rules disabled

Recommendation:

Keep ESLint at ^9.39.2 and block ESLint 10 upgrades in Renovate config:

{ packageRules: [{ matchPackageNames: ["eslint"], allowedVersions: "<10", description: "Block ESLint 10 until eslint-plugin-react@8.x is released" }] }

Timeline: March-April 2026 (waiting for eslint-plugin-react@8.x or eslint-config-next@16.2+)

Tracking: jsx-eslint/eslint-plugin-react#3699

claude · 2026-02-16T05:08:09Z

🚨 BLOCKING: ESLint 10 Breaking Change

This version upgrade breaks linting completely due to an incompatible transitive dependency.

Error:

TypeError: Error while loading rule 'react/display-name': contextOrFilename.getFilename is not a function

Root Cause:

eslint-plugin-react@7.37.5 (from eslint-config-next@16.1.6) only supports eslint ^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7 (see pnpm-lock.yaml:1703)

ESLint 10 changed the context API (getFilename() → filename property)

Impact:

❌ Linting completely broken

❌ CI/CD pipeline fails

❌ Pre-commit hooks fail

⚠️ Security rules not enforceable

Recommendation:

Keep ESLint at ^9.39.2 and block ESLint 10 upgrades in Renovate config:

{ "packageRules": [{ "matchPackageNames": ["eslint"], "allowedVersions": "<10", "description": "Block ESLint 10 until eslint-plugin-react@8.x is released" }] }

Expected Timeline: March-April 2026

Tracking:

eslint-plugin-react ESLint 10 support

Wait for eslint-plugin-react@8.x or eslint-config-next@16.2+

-Original file line number
+Diff line change
@@ Expand Up / @@ -56,7 +56,7 @@ @@
         "@vitest/ui": "4.0.18",
         "babel-plugin-react-compiler": "1.0.0",
         "concurrently": "9.2.1",
-        "eslint": "9.39.2",
+        "eslint": "10.0.0",
         "eslint-config-next": "16.1.6",
         "eslint-config-prettier": "10.1.8",
         "eslint-plugin-simple-import-sort": "12.1.1",
@@ Expand Down @@

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency eslint to v10 #1571

Uh oh!

Diff view

Diff view

There are no files selected for viewing

claude bot Feb 7, 2026

Uh oh!

claude bot Feb 8, 2026

Uh oh!

claude bot Feb 8, 2026

Uh oh!

claude bot Feb 9, 2026

Uh oh!

claude bot Feb 9, 2026

Uh oh!

claude bot Feb 9, 2026

Uh oh!

claude bot Feb 10, 2026

Uh oh!

claude bot Feb 10, 2026

Uh oh!

claude bot Feb 10, 2026

Uh oh!

claude bot Feb 11, 2026

Uh oh!

claude bot Feb 11, 2026

Uh oh!

claude bot Feb 11, 2026

Uh oh!

claude bot Feb 14, 2026

Uh oh!

claude bot Feb 16, 2026

Uh oh!

Uh oh!

Uh oh!

chore(deps): update dependency eslint to v10 #1571

Are you sure you want to change the base?

Uh oh!

chore(deps): update dependency eslint to v10 #1571

Uh oh!

Uh oh!

Diff view

Diff view

There are no files selected for viewing

claude bot Feb 7, 2026

Choose a reason for hiding this comment

⚠️ Breaking Change: ESLint 10 Incompatibility

Uh oh!

claude bot Feb 8, 2026

Choose a reason for hiding this comment

⚠️ Breaking Change: ESLint 10 Incompatibility

Uh oh!

claude bot Feb 8, 2026

Choose a reason for hiding this comment

⚠️ Breaking Change: ESLint 10 Incompatibility

Uh oh!

claude bot Feb 9, 2026

Choose a reason for hiding this comment

⚠️ Critical Breaking Change: ESLint 10 Incompatibility

Uh oh!

claude bot Feb 9, 2026

Choose a reason for hiding this comment

🚨 Critical Breaking Change: ESLint 10 Incompatibility

Uh oh!

claude bot Feb 9, 2026

Choose a reason for hiding this comment

🚨 Critical Breaking Change: ESLint 10 Incompatibility

Uh oh!

claude bot Feb 10, 2026

Choose a reason for hiding this comment

🚨 BREAKING: ESLint 10 Incompatibility

Uh oh!

claude bot Feb 10, 2026

Choose a reason for hiding this comment

🚨 CRITICAL: ESLint 10 Breaking Change

Error from CI

Root Cause

Impact Assessment

Recommendation: DO NOT MERGE

Why Not Workaround?

Uh oh!

claude bot Feb 10, 2026

Choose a reason for hiding this comment

🚨 BLOCKING: ESLint 10 Breaking Change

Uh oh!

claude bot Feb 11, 2026

Choose a reason for hiding this comment

🚨 BLOCKING: ESLint 10 Breaking Change

Uh oh!

claude bot Feb 11, 2026

Choose a reason for hiding this comment

🚨 BLOCKING: Incompatible Transitive Dependency

Uh oh!

claude bot Feb 11, 2026

Choose a reason for hiding this comment

🚨 BLOCKING: Incompatible Transitive Dependency

Uh oh!

claude bot Feb 14, 2026

Choose a reason for hiding this comment

🚨 BLOCKING: ESLint 10 Incompatibility

Uh oh!

claude bot Feb 16, 2026

Choose a reason for hiding this comment

🚨 BLOCKING: ESLint 10 Breaking Change

Uh oh!

Uh oh!

Uh oh!