- 05 Nov, 2025 20 commits
-
-
nextjs-bot authored
-
Joseph authored
-
nextjs-bot authored
-
Vercel Release Bot authored
This auto-generated PR updates the production integration test manifest used when testing Rspack.
-
Jiwon Choi authored
Since `generateStaticParams` runs in the background, when accessing the `devFallbackParams` during the render, it is still set to the previous result from the cache. Therefore, when the result has changed, re-render the RSC to sync the `devFallbackParams` with the new result. Closes NAR-491 --------- Co-authored-by:Josh Story <story@hey.com>
-
Benjamin Woodruff authored
`Glob::parse` is mostly called by the `Glob::new` turbo-task function which has an `RcStr`, so let's just use that instead of doing `RcStr` -> `&str` -> `String`.
-
nextjs-bot authored
Co-authored-by:Sebastian Sebbie Silbermann <sebastian.silbermann@vercel.com>
-
Benjamin Woodruff authored
- `experimental.ppr` was replaced with `cacheComponents`. - It's still in the zod and TS type schemas, I think for our error messages on the Next.js side, but Turbopack only needs to know about the fields that Turbopack cares about. Serde silently ignores unknown fields by default. - Nothing was reading this field from this struct. - This unit test coverage is very overkill.
-
Tobias Koppers authored
### What? use batch add to convert children to followers
-
Hendrik Liebau authored
Setting the cache status for a page in dev mode is a sequential operation that only requires the HTML request ID to identify WebSocket clients across different browser tabs/windows. This is different from connecting the React debug channel (after which the cache status handling was modeled), which requires both the HTML request ID as well as the request ID to correctly associate debug chunks for a given client with the matching request, which might be for the HTML document, a client-side navigation, or a server function call. With this PR, we're removing the unused `requestId` parameter from the `setCacheStatus` function. We're also renaming the WebSocket client's request ID to `htmlRequestId`, as well as renaming the associated maps and variables accordingly. This avoids confusion and better reflects the purpose of these IDs. One of those confusions was apparent in the `setReactDebugChannel` methods, which is now cleared up as well.
-
Sebastian "Sebbie" Silbermann authored
Suspense around body will trigger "missing tags" warning if something throws in the boundary. This error can come in slightly later and cause flaky test results. Fixes ``` ● Validations for <Link legacyBehavior> › When rendering from a Client Component › warns and throws an error if the child is lazy JSX expect(received).toMatchInlineSnapshot(snapshot) Snapshot name: `Validations for <Link legacyBehavior> When rendering from a Client Component warns and throws an error if the child is lazy JSX 1` ``` -- https://github.com/vercel/next.js/actions/runs/19097617827/job/54561506584#step:34:13256 -
Tim Neutkens authored
## What? Added the amount of workers used to the relevant steps as `using X workers`. Example: ``` ✓ Compiled successfully in 610.3ms ✓ Finished TypeScript in 954.4ms ✓ Collecting page data using 15 workers in 207.5ms ✓ Generating static pages using 15 workers (4/4) in 258.4ms ✓ Finalizing page optimization in 6.7ms ```
-
Tobias Koppers authored
This implements a portion of the first iteration of a bundle analyzer for Turbopack in Next.js by writing data files to disk. A separate visualization and explorer tool will follow. This data is written when builds are run with `next build --experimental-analyze`. An upcoming PR will implement a dedicated `next analyze` command that will write the data files without writing a complete build. The data is derived from Turbopack’s module and chunk graphs, and precise module sizes are reversed from the source map data of each chunk. Importantly, this requires that source maps are generated within Turbopack and the project is recomputed with them -- however, no source maps are written as part of the build artifacts if the user did not configure their Next.js config that way. The binary format written in these files is subject to change, so the feature is experimental for the time being. Until it stabilizes, no guarantees will be provided between it and the visualizer tool. Test Plan: In a test app: - do not configure `productionBrowserSourceMaps` - run `next build` and confirm **no files are written** to `.next/diagnostics/analyze` - run `next build --analyze` and confirm files **are** written to `.next/diagnostics/analyze` - Open the data with the yet-to-be-published visualization tool and confirm data is visible
-
Sebastian "Sebbie" Silbermann authored
-
Tobias Koppers authored
### What? use batch add in connect children
-
Benjamin Woodruff authored
It doesn't seem like it's worth pulling in this dependency anymore. Most of the places we need to serialize a regex, we use `EsRegex`, which handles serialization itself, and is a superset of `Regex`.
-
Joseph authored
-
Zack Tanner authored
Runtime prefetching relies on the presence of headers to determine caching behavior: `x-nextjs-postponed` indicates if the response was partial (so it knows if it should trigger a dynamic request to retrieve the missing data), and `x-nextjs-stale-time` provided stale time information to the client router. This worked fine in `next start` but due to how this is modeled in our Vercel deployment adapter, it was not possible to set runtime headers after the initial headers have been sent, as these requests were routed to prerenders. As a result of this limitation, this moves both the isPartial flag and the stale time value into the payload body. The response is run through a transform stream that replaces a sentinel value (`"rp": [sentinel]`) with the final stale time/isPartial values after we determine them. This avoids regenerating the entire RSC payload while ensuring correct values are sent to the client. Both properties are only included in runtime prefetch responses. Closes NAR-494 --------- Co-authored-by:Josh Story <story@hey.com>
-
Benjamin Woodruff authored
Turns out this is all dead code, so delete it! It looks like this was added back in https://github.com/vercel/turborepo/pull/3448, probably when Turbopack was trying to rewrite larger parts of Next.js than ended up happening.
-
Luke Sandberg authored
This data was mostly unused * allocation tracking was completely dead. So this saves a bit of memory and some data copies * duration tracking was only used for task statistics. This was a relatively new feature and not particularly useful. I considered wrapping it in a `feature` but dropping is simpler and this data is very redundant with tracing output anyway.
-
- 04 Nov, 2025 19 commits
-
-
Zack Tanner authored
This property is from back when we forked client router handling based off the presence of the `postponed` payload, but it's no longer being read by anything, so this PR removes it.
-
nextjs-bot authored
-
Benjamin Woodruff authored
This syntax isn't needed in modern rust. https://doc.rust-lang.org/reference/names/preludes.html#extern-prelude > Beginning in the 2018 edition, use declarations can reference crates in the extern prelude, so **it is considered unidiomatic to use extern crate**.
-
Vercel Release Bot authored
This auto-generated PR updates the development integration test manifest used when testing Rspack.
-
Niklas Mischkulnig authored
Closes PACK-5688 Closes https://github.com/vercel/next.js/issues/84766 1. Trace `new require("worker_threads").Worker` calls 2. ignore syntax errors in all traced files This does lead to a build error currently with cargo run --bin turbopack-nft -- --show-issues --graph bench/app-router-server/node_modules/thread-stream/index.js: ``` error - [analysis] [workspace]/node_modules/.pnpm/thread-stream@3.1.0/node_modules/thread-stream/test/syntax-error.mjs [workspace]/node_modules/.pnpm/thread-stream@3.1.0/node_modules/thread-stream/test/syntax-error.mjs:2:6 Parsing ecmascript source code failed 1 | // this is a syntax error + v 2 + import + ^ 3 | Expected 'from', got '<eof>' ``` Pulled in by this partly dynamic `new Worker()` call: https://github.com/pinojs/thread-stream/blob/82e011281b8895bf5e8f70008e0242927fcaf0cb/index.js#L53-L55 (Related to https://github.com/vercel/next.js/pull/84408, where this was previously fixed for extensionless files such as `LICENSE`)
-
Cong-Cong Pan authored
1. Fixed the incremental update bug in buildChunkGraph. 2. Fixed a bug in Rspack's built-in CssChunkingPlugin. For detailed release information, please see https://github.com/web-infra-dev/rspack/releases.
-
nextjs-bot authored
-
Jiwon Choi authored
`eslint-config-next` types were being emitted to `dist/src` instead of `dist/` during build. | Before | After | |--------|--------| | <img width="422" height="452" alt="CleanShot 2025-11-04 at 15 50 38@2x" src="https://github.com/user-attachments/assets/09c96d1a-41ba-4da9-87c6-bc05257c6e2a" /> | <img width="386" height="488" alt="CleanShot 2025-11-04 at 15 50 01@2x" src="https://github.com/user-attachments/assets/7b9802a4-e453-4086-90fb-a19e1aec7e20" /> | Fixes https://github.com/vercel/next.js/issues/85379 Closes: https://github.com/vercel/next.js/pull/84929 Closes: https://github.com/vercel/next.js/pull/85653
-
Niaz Morshed Nayeem authored
### What? Fix documentation typo in `refresh` function.
-
Joseph authored
Prepping for a bit more helpful work with these matchers
-
Tim Neutkens authored
## What? Fixes a small retainer object that is inserted on each request and not cleaned up. While at it also swapped array -> Set for the type checks to leverage `has` instead of `includes`.
-
Sebastian "Sebbie" Silbermann authored
-
Joseph authored
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
-
nextjs-bot authored
[diff facebook/react@561ee24d...67f7d47a](https://github.com/facebook/react/compare/561ee24d...67f7d47a) <details> <summary>React upstream changes</summary> - https://github.com/facebook/react/pull/35036 </details>
-
Niklas Mischkulnig authored
We had tree shaking enabled for NFT. That is incorrect however, as even unused imports (if you don't use any of the imported bindings, and the file is marked as `sideEffects: false`) are still needed at runtime, since Node.js will execute everything anyway. - I made the `treeShakingMode: None` explicit now (though that was already the `Default::default` anyway) - The real problem was that we still dropped side-effect free `ModulePart::Evaluation` references even when tree shaking was disabled. Closes #85172 Fixes PACK-5756
-
Niklas Mischkulnig authored
This abstraction was a leftover from when we had a swc_css and a lightningcss backend. Also inspired by https://github.com/vercel/next.js/pull/85524 as there was another constant-false `PartialEq` impl.
-
- 03 Nov, 2025 1 commit
-
-
nextjs-bot authored
-