Update nextjs monorepo to v13.4.0 #111
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/nextjs-monorepo"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
13.3.4
->13.4.0
13.3.4
->13.4.0
Release Notes
vercel/next.js
v13.4.0
Compare Source
Core Changes
next-types-plugin
causing Typescript errors when"type": "module"
is set: #49027experimentalReact
: #49046next/image
: #48997next/headers
: #48789next dev
failing for app when__NEXT_DISABLE_MEMORY_WATCHER
is set: #49056enableUndici: true
default and removenode-fetch
: #49061runtime
in layouts in type declarations: #49117ReadonlyHeaders
more compatible withHeaders
: #49075Blob
for Node.js < 18: #49156$$bound
if no closure argument is attached: #49188Documentation Changes
Example Changes
Misc Changes
swc_core
tov0.75.41
: #48982canary
branch: #49038app/page.tsx
: #49035Credits
Huge thanks to @kdy1, @alexkirsz, @sokra, @shuding, @dciug, @albertothedev, @DuCanhGH, @feedthejim, @li-jia-nan, @styfle, @kwonoj, @patrick91, @timneutkens, @balazsorban44, @ijjk, @padmaia, @Kikobeats, @huozhi, @sophiebits, @eps1lon, @reconbot, @acdlite, @jridgewell, and @sebmarkbage for helping!
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Renovate Bot.
c73e40304b
to2e1fd36e85