1. 05 Nov, 2025 20 commits
    • nextjs-bot's avatar
      v16.0.2-canary.9 · d787abba
      nextjs-bot authored
      d787abba
    • Joseph's avatar
      docs: getting started updates 01 (#85750) · 6ba8ec87
      Joseph authored
      6ba8ec87
    • nextjs-bot's avatar
      v16.0.2-canary.8 · 90d87598
      nextjs-bot authored
      90d87598
    • Vercel Release Bot's avatar
      Update Rspack production test manifest (#85795) · 6fde3cc7
      Vercel Release Bot authored
      This auto-generated PR updates the production integration test manifest used when testing Rspack.
      6fde3cc7
    • Jiwon Choi's avatar
      Sync devFallbackParams when generateStaticParams change (#85741) · a976c918
      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: 's avatarJosh Story <story@hey.com>
      a976c918
    • Benjamin Woodruff's avatar
      Turbopack: chore: Avoid string clones in Glob::parse by using RcStr (#85579) · 249fcec6
      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`.
      249fcec6
    • nextjs-bot's avatar
    • Benjamin Woodruff's avatar
      Turbopack: chore: Remove dead experimental.ppr struct field (#85792) · 4bf13443
      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.
      4bf13443
    • Tobias Koppers's avatar
      Turbopack: use batch add to add initial followers (#85624) · 5080ce53
      Tobias Koppers authored
      ### What?
      
      use batch add to convert children to followers
      5080ce53
    • Hendrik Liebau's avatar
      Resolve request ID confusion (#85809) · 937a3246
      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.
      937a3246
    • Sebastian "Sebbie" Silbermann's avatar
      [test] Deflake legacy-link-behavior (#85805) · 1226b535
      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
      1226b535
    • Tim Neutkens's avatar
      Build: Log amount of workers during static generation (#85706) · 831534c1
      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    
      ```
      831534c1
    • Tobias Koppers's avatar
      Turbopack: next build --analyze (#85197) · aae734b3
      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
      aae734b3
    • Sebastian "Sebbie" Silbermann's avatar
    • Tobias Koppers's avatar
      Turbopack: use batch add in connect children (#85623) · 15d0fd47
      Tobias Koppers authored
      ### What?
      
      use batch add in connect children
      15d0fd47
    • Benjamin Woodruff's avatar
      Turbopack: chore: Remove the serde_regex dependency, which wasn't very heavily used (#85578) · abdbdb71
      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`.
      abdbdb71
    • Joseph's avatar
      docs: fresh up getting started 00 (#85736) · 7fef3a0c
      Joseph authored
      7fef3a0c
    • Zack Tanner's avatar
      [runtime prefetching]: fix runtime prefetching when deployed (#85595) · 2f86fbab
      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: 's avatarJosh Story <story@hey.com>
      2f86fbab
    • Benjamin Woodruff's avatar
      Turbopack: chore: Remove dead RouteMatcher stuff (#85784) · e989fcb8
      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.
      e989fcb8
    • Luke Sandberg's avatar
      [turbopack] Drop duration and allocation tracking from CaptureFuture (#85534) · 67aa5f3d
      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.
      67aa5f3d
  2. 04 Nov, 2025 19 commits
  3. 03 Nov, 2025 1 commit