chore(deps-dev): bump eslint-config-next from 14.2.15 to 16.3.1 in /web - #39
Closed
dependabot[bot] wants to merge 1 commit into
Closed
chore(deps-dev): bump eslint-config-next from 14.2.15 to 16.3.1 in /web#39dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
Bumps [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next) from 14.2.15 to 16.3.1. - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](https://github.com/vercel/next.js/commits/v16.3.1/packages/eslint-config-next) --- updated-dependencies: - dependency-name: eslint-config-next dependency-version: 16.3.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/web/eslint-config-next-16.3.1
branch
from
August 21, 2026 23:01
e8509a1 to
2d5bd4f
Compare
edycutjong
added a commit
that referenced
this pull request
Aug 21, 2026
…ether Dependabot PRs #36 (eslint->10.8.1) and #39 (eslint-config-next->16.3.1) were mutually stuck: eslint-config-next@14 requires eslint ^7||^8, and eslint-config-next@16 requires eslint >=9, so neither could land alone against the other's peer constraint. Chose eslint 9.39.5 (latest 9.x, npm "maintenance" tag) over eslint 10: [email protected] itself only declares eslint >=9 with no upper bound, but its bundled typescript-eslint@^8.46.0 caps at "^8.57.0 || ^9.0.0" — eslint 10 fails that peer range and forces --legacy-peer-deps. eslint 9.39.5 satisfies eslint-config-next, typescript-eslint, eslint-plugin-react, eslint-plugin-import, eslint-plugin-jsx-a11y, and eslint-plugin-react-hooks cleanly. eslint-config-next@16 ships a native flat-config export (verified by inspecting the published tarball: dist/core-web-vitals.js does `module.exports = config` as a flat-config array), so eslint.config.mjs now imports `eslint-config-next/core-web-vitals` directly instead of bridging the old eslintrc-shaped config through FlatCompat. Dropped the now-unused `@eslint/eslintrc` devDependency. eslint-plugin-react-hooks bumped from the config's old bundled version to ^7.0.0, which adds new React Compiler purity rules (react-hooks/set-state-in-effect, react-hooks/purity) that flagged two pre-existing issues once the new rules actually started firing: count-up.tsx called setState synchronously in an effect body, and guard-list.tsx called Date.now() directly during render. Both fixed without behavior change (deferred via requestAnimationFrame and a useState lazy initializer, respectively). Verified `@next/next/no-img-element` still fires (as a warning) by temporarily adding a stray <img> and confirming eslint reported it, then reverting. Full Web · Quality job verified locally: npm ci (clean, no ERESOLVE), format:check, lint, typecheck, build, and test:unit all pass.
Owner
|
@dependabot rebase |
Contributor
Author
|
Looks like eslint-config-next is up-to-date now, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/web/eslint-config-next-16.3.1
branch
August 21, 2026 23:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps eslint-config-next from 14.2.15 to 16.3.1.
Release notes
Sourced from eslint-config-next's releases.
... (truncated)
Commits
3d32eb8v16.3.1d73f562v16.3.04fd843fv16.3.0-canary.1079480f7fv16.3.0-canary.106a8dcd25v16.3.0-canary.10538f0cdev16.3.0-canary.104f3edea1v16.3.0-canary.1030d5ff0dv16.3.0-canary.102cf1e001v16.3.0-canary.101267d6b1v16.3.0-canary.100Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for eslint-config-next since your current version.