1. 21 Jan, 2026 10 commits
    • nextjs-bot's avatar
      v16.2.0-canary.0 · 3fe7d63f
      nextjs-bot authored
      3fe7d63f
    • Hendrik Liebau's avatar
      [test] Fix deploy test of `cache-components.server-action.test.ts` (#88854) · a3500c32
      Hendrik Liebau authored
      When deployed, the sentinels where showing `at runtime` instead of `at
      buildtime`. There are two reasons for this:
      
      1. The page sentinel was accidentally rendered in a client component,
      which causes a hydration mismatch, and the value toggling from `at
      buildtime` to `at runtime` when the page is hydrated before the
      assertion is done.
      2. The middleware was setting sentinel cookies that are intended for the
      `/cookies/*` pages, but not for the `/server-action-inline` page. This
      caused the server action (which is triggered in the second test) to
      consider the page as revalidated, which then led the client router to
      refetch the page. With `next start` this is not a problem because the
      RSC response is prerendered at build time, and returned as a static
      file, which contains the correct sentinel values. However, when deployed
      on Vercel, the RSC request results in an ISR cache miss for some reason,
      which causes the page to be revalidated (with runtime sentinel values),
      and then the third test fails when it receives the regenerated response
      instead of the build-time prerender result. This needs to be
      investigated separately, but for now we disable the middleware from
      setting cookies on this page to prevent the ISR revalidation request.
      
      closes #88817
      closes NAR-740
      
      > [!TIP]
      > Best reviewed with hidden whitespace changes.
      a3500c32
    • Tobias Koppers's avatar
      Turbopack: show compressed size for print_cache_item_size (#88850) · bed512a3
      Tobias Koppers authored
      ### What?
      
      Improve the feature flag to show compressed size
      bed512a3
    • Hendrik Liebau's avatar
      [ci] Fix Rspack/Turbopack test manifest generation (#88845) · 71f9bda3
      Hendrik Liebau authored
      The recent change to always run all tests without aborting on failure
      (#88435) inadvertently broke manifest generation. Previously, test
      output was emitted for all tests when `NEXT_TEST_CONTINUE_ON_ERROR` was
      set, but that variable was removed. Now test output is only emitted for
      failing tests, causing the manifest to lose all passing test entries.
      
      This adds a new `NEXT_TEST_EMIT_ALL_OUTPUT` environment variable that
      restores the full output behavior specifically for the manifest
      generation workflows.
      71f9bda3
    • Niklas Mischkulnig's avatar
    • Tobias Koppers's avatar
      Turbopack: shrink amortized (#88619) · 1bdb2e20
      Tobias Koppers authored
      ### What?
      
      Use amortized shrinking.
      
      Capacity should always be a power of 2.
      We shrink when len is capacity / 3.
      Assuming the capacity was `2^x` we shrink to `2^(x-1)` which is
      `capacity / 2`.
      Therefore capacity is still larger than len, which avoids direct
      reallocation when items are added again.
      1bdb2e20
    • Niklas Mischkulnig's avatar
      1818b104
    • Hendrik Liebau's avatar
    • Andrew Clark's avatar
      Embed static sibling info in route tree (#88692) · d3de9bce
      Andrew Clark authored
      This change adds infrastructure for a planned client-side optimization
      where the router can infer route structure from previously prefetched
      routes, avoiding redundant route tree requests.
      
      When the client prefetches /blog/post-1 and learns the route structure
      is /blog/[slug], it could potentially reuse that knowledge for
      /blog/post-2 without another server roundtrip. However, if a static
      route like /blog/featured exists at the same level, the client needs to
      know NOT to apply the dynamic template for that URL.
      
      staticSiblings provides this information. When a dynamic segment like
      [slug] has static siblings (e.g., "featured", "archive"), the server
      includes them in the prefetch response. The client can then check
      whether an incoming URL matches a known static sibling, and if so,
      recognize that the previously learned route structure does not apply.
      d3de9bce
    • Andrew Clark's avatar
      Reuse bfcache data during Full prefetches (#88606) · fc65fbb0
      Andrew Clark authored
      During a Full prefetch (`<Link prefetch={true}>`), check the bfcache for
      matching segment data before issuing a new request. The bfcache stores
      data from previous navigations, which always includes dynamic data.
      
      This optimization avoids redundant server requests when the user has
      already navigated to a route and the data is still fresh according to
      the staleTimes.dynamic configuration.
      fc65fbb0
  2. 20 Jan, 2026 17 commits
  3. 19 Jan, 2026 13 commits