Repository navigation
Update dependency eslint-config-next to v16 - #620
renovate[bot] wants to merge 1 commit into
Conversation
|
e4823e4 to
aff4108
Compare
9cbd464 to
b461dd0
Compare
b461dd0 to
e8c8ade
Compare
e6f6ca3 to
a577c46
Compare
a577c46 to
8b893aa
Compare
8b893aa to
e672924
Compare
33bf0c9 to
04443e2
Compare
04443e2 to
ea7ce16
Compare
8f3eb09 to
4b4ce6a
Compare
5bbbeaf to
12cdefc
Compare
790ca53 to
dd04458
Compare
1fc610b to
eb9eca5
Compare
075fa35 to
5563805
Compare
000a7d3 to
5dc7a6a
Compare
8ed3619 to
dbdae08
Compare
8bd03bc to
223f6cb
Compare
79eaeb9 to
355f359
Compare
355f359 to
6bb38d8
Compare
b39d058 to
66c3205
Compare
7525df0 to
81794fa
Compare
e128b54 to
16f93e0
Compare
bba3726 to
d613c85
Compare
f929b0f to
b54ec95
Compare
| "@typescript-eslint/parser": "^8.60.1", | ||
| "eslint": "^8.57.1", | ||
| "eslint-config-next": "^15.5.19", | ||
| "eslint-config-next": "^16.0.0", |
There was a problem hiding this comment.
🟡 Next lint config has incompatible ESLint peer
Installing eslint-config-next 16.3.6 with strict peer checks fails because its ESLint peer requires version 9 or newer. The workspace still locks eslint to 8.57.1.
Learn more
The workspace uses ESLint 8.57.1, while the updated config declares eslint: >=9.0.0 in its peer dependencies. pnpm records this mismatch in the lockfile but installs can reject it when strict peer checking is enabled. The existing ESLint configuration does not extend the Next preset, so simply changing the root ESLint major also requires checking the other shared lint presets.
Example: With strict-peer-dependencies=true, installing this lockfile rejects the Next config's ESLint peer instead of completing dependency installation.
Recommended fix: Align eslint-config-next and the root eslint to compatible majors; if upgrading ESLint, validate the shared .eslintrc and other installed ESLint presets before updating the lockfile.
Was this helpful? React with 👍 or 👎 to provide feedback.
b54ec95 to
1aae89c
Compare
1aae89c to
c0278bc
Compare
This PR contains the following updates:
^15.5.19→^16.0.0Release Notes
vercel/next.js (eslint-config-next)
v16.3.6Compare Source
This release contains a security fix for GHSA-vcvr-r3jv-pc5j: Remote Code Execution in next/og ImageResponse
v16.3.5Compare Source
The following bug fixes have been backported. It does not include all pending features/changes on canary.
output: 'standalone'is used with an adapter (#98167)use cacheprerender signal retention (#98448)v16.3.4Compare Source
Follow-up release to v16.3.3 re-enabling AVIF Image Optimization (#97949).
The following bug fixes have been backported. It does not include all pending features/changes on canary.
Credits
Huge thanks to @eps1lon, @mischnic, and @timneutkens for helping!
v16.3.3Compare Source
This release contains security fixes for the following advisories:
Critical:
v16.3.2Compare Source
Core Changes
Credits
Huge thanks to @lubieowoce, @unstubbable, @timneutkens, @mischnic, and @eps1lon for helping!
v16.3.1Compare Source
What's Changed
turbopack_ecmascriptandturbopack_wasm's embeded FS tointernal_assets_conditionsby @lukesandberg in #96655headers()view of the incoming request by @unstubbable in #97311'use cache'files by @unstubbable in #97312unstable_cacheby @unstubbable in #97313Full Changelog: vercel/next.js@v16.3.0...v16.3.1
v16.3.0Compare Source
Core Changes
{eval:true}in worker_threads constructors: #91666cacheComponents: #91711next internal post-buildCLI command for Turbopack database compaction: #91336Effectas a trait instead of a closure: #89080AggregateError.errorsin the error overlay: #91835varyParamstracking for Cached Navigations: #92113experimental.dynamicIOconfig: #92081entry-base.ts: #91527get_compilation_issuestool and NAPI method: #92062next devserver if.nextis deleted: #92135turbo_tasks::apply_effects, useEffects::applyinstead: #91858CURRENTand stale sst files: #92414minimumReleaseAgeExcludefor React and friends: #9253574568e86-20260328to404b38c7-20260408: #92536targetoption in React Compiler for Pages + React 18: #91500compilerOptions.pathsin tsconfigs withoutcompilerOptions.baseUrl: #92277@turbopack/base64module: #92549"use cache": #92736downlevelIteration: #92652baseUrl: #92653@next/swcbinary postinstall: #92813"use cache"args during final prerender: #92820moduleResolution: "node": #92654images.maximumResponseBodyapplies to local images too: #92920unstable_io: #92923'use cache'invocations: #91830'use cache': #93055'use cache'fill timeout configurable: #93070url.parse: #93208super(...)messages in Error subclass constructors: #93182__NEXT_ERROR_CODEacross the/_errorpage handoff: #93183next build: #93280export * as X from './self'in scope-hoisted modules: #93192expirevalue with blocking revalidation: #93211experimental.turbopackWorkerAssetPrefixto keep Workers same-origin whenassetPrefixis a CDN: #93271onErroronce: #93209other: #93206cacheHandlerskeys: #93453compilerOptions: #93377'use cache'module-scope deadlocks early in dev: #93500'use cache'deadlock probe worker: #93538ReferencedAsset::from_resolve_resultas a turbotask: #93297rcstr!macro_rules with proc macro: #93551searchParamsaccess through a Proxy to catch missing-key reads: #93549cacheSignalacrossunstable_cacheforeground revalidation: #93617unstable_io: #93621Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.