Bump eslint from 9.39.4 to 10.8.1 - #33
Conversation
Bumps [eslint](https://github.com/eslint/eslint) from 9.39.4 to 10.8.1. - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](eslint/eslint@v9.39.4...v10.8.1) --- updated-dependencies: - dependency-name: eslint dependency-version: 10.8.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| "@vitejs/plugin-rsc": "0.5.26", | ||
| "drizzle-kit": "0.31.10", | ||
| "eslint": "9.39.4", | ||
| "eslint": "10.8.1", |
There was a problem hiding this comment.
🟡 Installing project dependencies can fail because the linter's new major version is rejected by the Next.js lint plugins
The linter is upgraded to a new major version ("eslint": "10.8.1" at package.json:51) while several plugins bundled with the Next.js lint preset still declare support only up to the previous major, so a fresh dependency install can be rejected.
Impact: Contributors and CI may be unable to install dependencies or run the lint step until the plugins are updated or peer conflicts are explicitly bypassed.
Peer dependency ranges in the lockfile cap the linter at v9
eslint-config-next@16.2.6 (package-lock.json:6184-6199) pulls in eslint-plugin-import@2.32.0, eslint-plugin-jsx-a11y, and eslint-plugin-react, whose recorded peer ranges are "eslint": "^2 || ... || ^9" (package-lock.json:6295), "^3 || ... || ^9" (package-lock.json:6335), and "^3.0.0 || ... || ^9.7" (package-lock.json:6368). With root eslint@10.8.1 (package-lock.json:6125-6128) and no nested v9 copy, npm install resolves these peers against v10 and reports ERESOLVE unless --legacy-peer-deps/--force is used. The lockfile in this PR appears to have been produced with peer checks relaxed, so npm ci may still work while a plain npm install (and the npm run lint gate required by CONTRIBUTING.md step 3) breaks.
Prompt for agents
The eslint major bump to 10.8.1 conflicts with peer dependency ranges of plugins bundled by eslint-config-next@16.2.6 (eslint-plugin-import 2.32.0, eslint-plugin-jsx-a11y, eslint-plugin-react all cap eslint at ^9 per package-lock.json). Verify that a clean `npm install` and `npm run lint` succeed on this branch; if they don't, either hold the bump until eslint-config-next ships plugin versions that declare eslint ^10 support, or bump eslint-config-next / add explicit overrides so peer resolution succeeds without --legacy-peer-deps.
Was this helpful? React with 👍 or 👎 to provide feedback.
| "@vitejs/plugin-rsc": "0.5.26", | ||
| "drizzle-kit": "0.31.10", | ||
| "eslint": "9.39.4", | ||
| "eslint": "10.8.1", |
There was a problem hiding this comment.
🔍 Major eslint bump may surface new/renamed rules through eslint-config-next
This is a major version jump (9.x → 10.x) of the linter used by eslint.config.mjs, which imports eslint/config (defineConfig, globalIgnores) and the eslint-config-next/core-web-vitals and /typescript presets. Major ESLint releases typically change default rule severities, remove deprecated formatters/rules, and tighten config-file validation, so the repo's npm run lint gate (required by CONTRIBUTING.md step 3) should be run on this branch before merging to confirm no new violations or config validation errors surface. Node engines (>=22.13.0 in package.json:6) satisfy eslint 10's ^20.19.0 || ^22.13.0 || >=24 requirement (package-lock.json:6170), so runtime support is fine.
Was this helpful? React with 👍 or 👎 to provide feedback.
Bumps eslint from 9.39.4 to 10.8.1.
Release notes
Sourced from eslint's releases.
... (truncated)
Commits
c049dc310.8.1a3f7826Build: changelog update for 10.8.118eb0a7fix: prevent ASI hazard inno-unused-labelsautofix (#21173)0a14800chore: update github/codeql-action action to v4.37.4 (#21196)7d0cbf8docs: Update README05adcb1test: fix failing ecosystem test foreslint-plugin-unicorn(#21191)5611035test: add error locations info tono-void(#21185)ee47333ci: bump github/codeql-action from 4 to 4.37.3 (#21176)f131c03chore: improve ecosystem test failure reporting (#20937)0a05812docs: add missing backticks tono-duplicate-imports.js(#21183)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)