Update dependency @next/eslint-plugin-next to v16#2772
Conversation
7557cd1 to
f62137d
Compare
4c980bd to
d8a2959
Compare
1858b47 to
34d9c1e
Compare
62ac883 to
50eeb99
Compare
5a4c6e2 to
6855951
Compare
OpenAPI ChangesNo changes detected Unexpected changes? Ensure your branch is up-to-date with |
| "version": "0.0.0", | ||
| "devDependencies": { | ||
| "@next/eslint-plugin-next": "^14.2.7", | ||
| "@next/eslint-plugin-next": "^16.0.0", |
There was a problem hiding this comment.
Bug: The upgrade to @next/eslint-plugin-next v16 requires a new "flat config" format, but the project still uses the legacy .eslintrc.js, which will cause the CI linting step to fail.
Severity: CRITICAL
Suggested Fix
Migrate the ESLint configuration from the legacy .eslintrc.js file to the new flat config format by creating an eslint.config.js or eslint.config.mjs file. This will align the project with the requirements of @next/eslint-plugin-next v16 and ensure the linting process runs correctly.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: frontends/package.json#L38
Potential issue: The project upgrades `@next/eslint-plugin-next` to v16, which is
designed for ESLint's new "flat config" format (`eslint.config.js`). However, the
repository's configuration remains in the legacy `.eslintrc.js` format. This
incompatibility will cause the `yarn lint-check` command, executed during the CI "Lints"
step, to fail with a configuration error. The linter will be unable to correctly load
the Next.js plugin preset, breaking the CI pipeline.
| "version": "0.0.0", | ||
| "devDependencies": { | ||
| "@next/eslint-plugin-next": "^14.2.7", | ||
| "@next/eslint-plugin-next": "^16.0.0", |
There was a problem hiding this comment.
Bug: Upgrading @next/eslint-plugin-next to v16 is incompatible with the project's legacy .eslintrc.js configuration, which will cause the lint-check command to fail in CI.
Severity: HIGH
Suggested Fix
To resolve this, either migrate the ESLint configuration from the legacy .eslintrc.js to the new eslint.config.js (flat config) format as recommended by Next.js v16, or avoid upgrading @next/eslint-plugin-next until the configuration migration is complete.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: frontends/package.json#L38
Potential issue: The project's `frontends/package.json` is being updated to use
`@next/eslint-plugin-next` version 16. This new version of the plugin is designed for
ESLint's new "flat config" format and is not backward compatible with the legacy
`.eslintrc.js` file used in the project. When the `yarn lint-check` command runs in CI,
ESLint (version 8.57.1) will attempt to load the shareable config
`"plugin:@next/next/recommended"`. However, the v16 plugin likely no longer exports this
in the expected legacy format, which will cause a runtime error during the linting
process and fail the CI build.
This PR contains the following updates:
^14.2.7→^16.0.0Release Notes
vercel/next.js (@next/eslint-plugin-next)
v16.2.6Compare Source
This release contains security fixes for the following advisories:
High:
Moderate:
Low:
v16.2.5Compare Source
This release contains security fixes for the following advisories:
High:
Moderate:
Low:
v16.2.4Compare Source
Core Changes
Credits
Huge thanks to @Badbird5907, @lukesandberg, @andrewimm, @sokra, and @mischnic for helping!
v16.2.3Compare Source
Core Changes
Credits
Huge thanks to @icyJoseph, @sokra, @wbinnssmith, @eps1lon and @ztanner for helping!
v16.2.2Compare Source
Core Changes
Credits
Huge thanks to @nextjs-bot, @icyJoseph, @ijjk, @gaojude, @wbinnssmith, @lukesandberg, and @bgw for helping!
v16.2.1Compare Source
Core Changes
cacheComponents(#91711){eval:true}in worker_threads constructors (#91666)Credits
Huge thanks to @icyJoseph, @abhishekmardiya, @ijjk, @mischnic, @unstubbable, @sokra, and @lukesandberg for helping!
v16.2.0Compare Source
Core Changes
f93b9fd4-20251217to65eec428-20251218: #87323experimental.strictRouteTypesconfig: #87378satisfieswhen validating page and route modules: #87398numberinconfig.api.bodyParser.sizeLimitwhen validating route: #87633images.maximumResponseBodyconfig: #88183'use cache'wrapper: #88219'use cache'function calls: #86920pending revalidates...debug log if applicable: #88221noUncheckedSideEffectImportsfor CSS imports: #88199/_next/routes: #8835365eec428-20251218to3e1abcc8-20260113: #88530interopDefault: #884863e1abcc8-20260113to4a3d993e-20260114: #885474a3d993e-20260114tobef88f7c-20260116: #88649--debug-build-pathsbracket escaping for glob patterns: #88660--debug-build-paths: #88654next start --inspect: #88744--debug-build-pathssupport to filter routes: #88655bef88f7c-20260116to41b3e9a6-20260119: #8875641b3e9a6-20260119tod2908752-20260119: #88774rewroteURLtorewrittenPathnamein request metadata: #88751getImplicitTagsto accept pathname instead of url object: #88753NEXT_DEPLOYMENT_IDglobal: #86738<html data-dpl-id>and don't inline it into JS anymore: #88761revalidatePathwith params and trailing slash when deployed: #88623d2908752-20260119tob546603b-20260121: #88860deploymentIdfrom App RouterRenderOptsPartial: #88866b546603b-20260121to24d8716e-20260123: #88963?dpl=to all asset urls returned by Turbopack: #88828useEffectEventto disallowed React APIs in Server Components: #88985renderOpts.nextExporttoisBuildTimePrerendering: #88951README.mds: #89022__turbopack_load_by_url__with query: #8889924d8716e-20260123to8c34556c-20260126: #89066baseline-browser-mappingwarnings: #89175.mdlicenses are included in vendored packages: #8920110680271-20260126to230772f9-20260128: #89250tarused to extract SWC binary : #89158browserslistdoesn't issue outdated warnings forbaseline-browser-mapping: #89287230772f9-20260128toda641178-20260129: #89301rules.*.typeconfig to allow changing the type of a module: #88788logging.serverFunctions: #89321'use cache'functions: #89408da641178-20260129toed4bd540-20260202: #89401ed4bd540-20260202tob1533b03-20260203: #89444b1533b03-20260203to3e00319b-20260203: #89449experimental.reportSystemEnvInliningfor Turbopack: #89304instant(): #89469cacheLifeon outer"use cache"when nesting short-lived caches: #894813e00319b-20260203to95ffd6cd-20260205: #89550discoverRoutes()API: #8897195ffd6cd-20260205to2dd9b7cf-20260208: #89681AggregateError.errorsin terminal output: #889992dd9b7cf-20260208to272441a9-20260209: #89722next dev: #89798type: "text"under a new experimental flag, following what webpack did: #89560use: #89793experimental.appNewScrollHandler: #83107272441a9-20260209to6066c782-20260212: #89923--debug-prerenderis set: #89834require.resolve()to get the installednextversion: #89166prefetch={true}on Links to routes withinstant: #900616066c782-20260212to4842fbea-20260217: #90144pnpm build: #89819images.maximumDiskCacheSize: #89963isPartialbyte stripping when deployed: #902722ba30655-20260219toab18f33d-20260220: #90279: #90152
ignoreListof 3rd party sourcemaps in Redbox: #90317AggregateError: #90391config.reactProductionProfilingfor Webpack: #90430rust-toolchain: #90442ab18f33d-20260220toc0060cf2-20260224: #90452NEXT_TEST_NATIVE_DIRis specified: #90387unstable_instantis used in Client Component: #90396experimental.reactDebugChannelby default: #90310c0060cf2-20260224to98ce535f-20260226: #90605Configuration
📅 Schedule: (in timezone US/Eastern)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.