- 26 Jan, 2026 7 commits
-
-
nextjs-bot authored
-
Wyatt Johnson authored
Adds a configurable `experimental.maxPostponedStateSize` limit for PPR postponed state body parsing to prevent OOM/DoS attacks. The postponed state body was read entirely without size limits, creating a potential denial-of-service vector through unbounded memory allocation. Enforces a 10 MB default limit (configurable via next.config.js) with byte counting during body parsing. Returns HTTP 413 when exceeded with a helpful error message directing users to increase the limit if needed. <!-- Closes NEXT- --> <!-- Fixes # -->
-
Steven authored
Based on our metrics, the P99.9 for a source image is 47 MB so we can adjust the default setting to be much lower (by changing from from 300 MB to 50 MB) in favor of reducing memory.
-
Steven authored
Add `images.maximumResponseBody` configuration to exit early when attempting to optimize large source images.
-
Hendrik Liebau authored
-
Sebastian "Sebbie" Silbermann authored
Backports https://github.com/vercel/next.js/pull/88647 --- [Slack Thread](https://vercel.slack.com/archives/C03S8ED1DKM/p1768574003809109?thread_ts=1768574003.809109&cid=C03S8ED1DKM) <a href="https://cursor.com/background-agent?bcId=bc-57689c0b-287b-43f1-87ca-756ee7754a69"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/open-in-cursor-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/open-in-cursor-light.svg"><img alt="Open in Cursor" src="https://cursor.com/open-in-cursor.svg"></picture></a> <a href="https://cursor.com/agents?id=bc-57689c0b-287b-43f1-87ca-756ee7754a69"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/open-in-web-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/open-in-web-light.svg"><img alt="Open in Web" src="https://cursor.com/open-in-web.svg"></picture></a>
-
Joseph authored
A handful of PRs to sync w/ next patch release --------- Co-authored-by:
Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com> Co-authored-by:
vercel[bot] <35613825+vercel[bot]@users.noreply.github.com> Co-authored-by:
Hanzala Sohrab <sorb.hanzala@gmail.com>
-
- 23 Jan, 2026 1 commit
-
-
Joseph authored
Back porting docs updates into 16-1 (canary now contains changes that shouldn't show in 16.1) --------- Co-authored-by:
Eng Zer Jun <engzerjun@gmail.com> Co-authored-by:
Rich Haines <hello@richardhaines.dev> Co-authored-by:
Tim Neutkens <tim@timneutkens.nl> Co-authored-by:
vercel[bot] <35613825+vercel[bot]@users.noreply.github.com> Co-authored-by:
Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com> Co-authored-by:
Luke Sandberg <lukesandberg@users.noreply.github.com> Co-authored-by:
graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com> Co-authored-by:
Jiachi Liu <inbox@huozhi.im> Co-authored-by:
Vercel <vercel[bot]@users.noreply.github.com>
-
- 19 Jan, 2026 2 commits
-
-
nextjs-bot authored
-
JJ Kasper authored
Backports https://github.com/vercel/next.js/pull/88733Co-authored-by:
Niklas Mischkulnig <4586894+mischnic@users.noreply.github.com>
-
- 16 Jan, 2026 3 commits
-
-
nextjs-bot authored
-
Zack Tanner authored
Backports: - https://github.com/vercel/next.js/pull/87991/changes/4b46a382b77b89cb3a23a00888e5563c06b93f4cCo-authored-by:
Andrew Clark <git@andrewclark.io>
-
Niklas Mischkulnig authored
Backport https://github.com/vercel/next.js/pull/88253 into 16.1 Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
- 14 Jan, 2026 3 commits
-
-
nextjs-bot authored
-
Niklas Mischkulnig authored
Co-authored-by:xusd320 <xusd320@gmail.com>
-
Benjamin Woodruff authored
Co-authored-by:
Jimmy Lai <laijimmy0@gmail.com> Co-authored-by:
Claude Opus 4.5 <noreply@anthropic.com> Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
- 09 Jan, 2026 1 commit
-
-
Benjamin Woodruff authored
This is a backport of https://github.com/vercel/next.js/pull/87841 to the `next-16-1` branch.
-
- 22 Dec, 2025 3 commits
-
-
nextjs-bot authored
-
Benjamin Woodruff authored
Next 16.1 changed Turbopack's external packaging to use symlinks. Symlinks require elevated privileges on Windows if "Developer Mode" is not enabled. We can work around this by using junction points, which are mostly equivalent, but: - They only work with directories. - They can only point to absolute paths, not relative paths. Fixes #87334 Fixes #87607 Fixes #87603 Fixes #87605 Fixes #87559 Fixes #87604 Fixes #87601 Fixes #87599 Fixes #87598 Fixes #87596 Fixes #87595 Fixes #87592 Fixes #87590 Fixes #87589 Fixes #87473 Fixes #87586 Fixes #87585 Fixes #87584 Fixes #87583 Fixes #87582 Fixes #87576 Fixes #87575 Fixes #87574 Fixes #87573 Fixes #87572 Fixes #87571 Fixes #87568 ... and many more Also: Fixes #69858 (related issue about `output: 'standalone'` on Windows. ## Testing - Disable Developer Mode on Windows, reboot, and then verify that symlink creation fails. - Make a payload app with `pnpx create-payload-app` (just pick sqlite for the database when prompted), and then update the app with `pnpx @next/codemod upgrade 16.1.0`. - Add `output: 'standalone'` to the `next.config.js`. - Try running `pnpm build` --------- Co-authored-by:Tobias Koppers <tobias.koppers@googlemail.com>
-
nextjs-bot authored
-
- 18 Dec, 2025 10 commits
-
-
nextjs-bot authored
-
nextjs-bot authored
-
Zack Tanner authored
Reverts vercel/next.js#86752 This has consequences when `.next` is in `exclude`. Reverting for now.
-
nextjs-bot authored
-
Jiachi Liu authored
-
Cong-Cong Pan authored
Rspack now enables persistent caching by default. ## Performance Comparison ### Pages Router I benchmarked performance using this repo: https://github.com/SyMind/chakra-ui-docs/tree/next-rspack to test the Next.js pages router. I tested the performance with the following steps: 1. Execute `pnpm run dev` 2. Wait for the server to be ready (indicated by the 'Ready' message) 3. Run curl on the root endpoint (/) Each build was run 5 times, and the shortest time to reach "Compiled successfully" was recorded. Test environment: Apple M1 Pro CPU | Tool | Build without cache | Build with cache | Dev without cache | Dev with cache | |-------------|---------------------|------------------|---------------------------------|----------------| | Rspack | 3.8s | 2.6s | 1.7s | 3ms | | Webpack | 14.0s | 4.0s | 7.8s | 3.2s | ### App Router I benchmarked performance using this repo: https://github.com/SyMind/shadcn-ui/tree/next-rspack to test the Next.js app router. I tested the performance with the following steps: 1. Execute `pnpm run dev` or `pnpm run build` 2. Wait for the server to be ready (indicated by the 'Ready' message) 3. Run curl on the root endpoint (/) Each build was run 5 times, and the shortest time to reach "Compiled successfully" was recorded. Test environment: Apple M1 Pro CPU | Bundler | Build (No Cache) | Build (Cache) | Dev (No Cache) | Dev (Cache) | |------------|----------------------|-------------------|--------------------|-----------------| | Rspack | 12.3s | 5.9s | 7.1s | 1941ms | | Webpack | 27.0s | 13.0s | 11s | 9.6s | ## About Rspack Persistent Cache Strategy > packages/next/src/server/dev/hot-reloader-rspack.ts Rspack's persistent caching differs from Webpack in how it manages module graphs. While Webpack incrementally updates modules, Rspack operates on complete module graph snapshots for cache restoration. Problem: - Next.js dev server starts with no page modules in the initial entry points - When Rspack restores from persistent cache, it finds no modules and purges the entire module graph - Later page requests find no cached module information, preventing cache reuse Solution: - Track successfully built page entries after each compilation - Restore these entries on dev server restart to maintain module graph continuity - This ensures previously compiled pages can leverage persistent cache for faster builds ## Note I have updated the test case configuration in `test/integration/telemetry/next.config.use-cache` to disable persistent cache. This is because, whether using webpack or Rspack, when persistent caching is enabled, modules are no longer recompiled by loaders, which prevents the Telemetry plugin from collecting information. Please note that this issue also exists with webpack. You can reproduce it locally by running `pnpm run test test/integration/telemetry/test/config.test.js` twice.
-
Will Binns-Smith authored
-
Luke Sandberg authored
Drop some references so there is a plausible path to updating these in the future
-
Will Binns-Smith authored
-
nextjs-bot authored
-
- 17 Dec, 2025 10 commits
-
-
nextjs-bot authored
-
Sebastian "Sebbie" Silbermann authored
-
Zack Tanner authored
Fixes a few failing deployment tests that weren't validated when landed last week. - next.cliOutput is not available when deployed because it's part of runtime logs - status code changes on Vercel because POSTing to a static 404 page is treated differently.
-
Will Binns-Smith authored
This functionality was added late in #87258 but was broken as we needed to pass this along to the Rust side. We'd also need to be able to write to arbitrary absolute paths there, so let's punt on it. Test Plan: e2e tests
-
Hendrik Liebau authored
-
nextjs-bot authored
-
Will Binns-Smith authored
-
Vercel Release Bot authored
This auto-generated PR updates font data with latest available Co-authored-by:nextjs-bot <it+nextjs-bot@vercel.com>
-
Will Binns-Smith authored
The top bar is getting quite wide with all of its button toggle groups. This: - Converts the Compressed/Uncompressed and Client/Server toggles to shadcn `<Select>`s - Adds a custom `<MultiSelect>` implementation since this is missing in shadcn. This composes shadcn’s popovers and a series of checkboxes, along with accessibility attributes and keyboard shortcuts. - Uses this `<MultiSelect>` for the type filter - Removes the divider between these since there aren’t any groups left to divide <img width="1547" height="719" alt="image" src="https://github.com/user-attachments/assets/4041f6b7-2a47-4e17-b020-448ac0103740" />
-
Cong-Cong Pan authored
update @next/rspack-core version to 1.0.2 and update the snapshot other changes: - packages/next/src/build/webpack-config.ts Adjusted configuration to account for differences in default node config between Rspack and Webpack. - packages/next/src/shared/lib/format-webpack-messages.ts Added a fallback to moduleIdentifier in cases where Rspack does not correctly populate moduleName.
-