1. 05 Feb, 2026 2 commits
  2. 04 Feb, 2026 14 commits
    • nextjs-bot's avatar
      v16.2.0-canary.27 · ab8e7865
      nextjs-bot authored
      ab8e7865
    • Janka Uryga's avatar
      [CC] Rename "unstable_prefetch" to "unstable_instant" (#89448) · 812996cc
      Janka Uryga authored
      Mostly mechanical rename.
      
      Also changes the error page to `errors/invalid-instant-configuration`.
      I'm not really worried about dangling links here because this is a new
      API and we don't expect anyone to be using it yet.
      812996cc
    • Andrew Clark's avatar
      Add experimental flag to expose testing API in production builds (#89499) · 12f85450
      Andrew Clark authored
      ## Summary
      
      Adds `experimental.exposeTestingApiInProductionBuild` to make the
      Instant Navigation Testing API available in production builds. This is a
      stopgap until a dedicated "profiling build" mode exists—similar to
      React's profiling builds that include extra instrumentation without the
      dev-mode overhead.
      
      The testing API lets e2e tests assert on prefetched UI before dynamic
      data streams in. Previously it was dev-only, but production builds have
      different timing characteristics (prefetches complete faster, code paths
      differ), so testing against production builds is valuable.
      
      ## Approach
      
      Introduces a single bundler environment variable
      `process.env.__NEXT_EXPOSE_TESTING_API` that's true when either:
      - Running in dev mode, OR
      - The experimental flag is enabled
      
      This replaces scattered `NODE_ENV !== 'production'` checks throughout
      the testing API code paths, making the gating logic consistent and
      centralized in the build configuration.
      
      Also renames `dev-navigation-lock.ts` to `navigation-testing-lock.ts`
      and updates header/cookie names from "dev-only" to
      "instant-navigation-testing" to reflect that the API is no longer
      dev-exclusive.
      
      ## Test plan
      
      - Updated existing e2e tests to run in both dev and production modes
      - Tests pass with `NEXT_TEST_MODE=start` (production build)
      12f85450
    • Jiachi Liu's avatar
      Include owner stack for forwarded errors if available (#89493) · 99c8038e
      Jiachi Liu authored
      For forwarded logs, we can also attach the owner stack if it's
      available, then we can see the proper errors trace shown in the
      terminal.
      
      In this way agent can directly detect where the error is happening from
      reading terminal log, and fix it
      
      | After | Before |
      |:---|:---|
      | <img width="937" height="778" alt="image"
      src="https://github.com/user-attachments/assets/666cc012-4e79-41f4-9d6f-b9c1969316bf"
      /> | <img width="942" height="641" alt="image"
      src="https://github.com/user-attachments/assets/a44f795a-d297-4fb8-9efe-25e6e3684014"
      /> |
      99c8038e
    • Niklas Mischkulnig's avatar
      Handle Pages data route skew with deployment id header, take 2 (#89325) · 49e0a8a8
      Niklas Mischkulnig authored
      Reapply https://github.com/vercel/next.js/pull/88959
      Revert https://github.com/vercel/next.js/pull/89323
      
      
      Closes PACK-6537
      Closes PACK-6756
      
      - Deployment skew (forcing a MPA nav instead of a SPA nav if a deployment happened inbetween) is handled by comparing a header on the client side.
          - The other case that used build ids was app router, which was changed to the same approach in https://github.com/vercel/next.js/pull/88855
      - Then, when a deployment id is available, make the build id a constant
      	- Particularly, this makes the rollout of this much easier as the data route paths stay the same (both in Next.js itself as well as in the builder)
      
      
      If you use `output:export` and set `config.deploymentId` (i.e. enable skew protection) you are still expected to set these headers.
      49e0a8a8
    • Eric Rabinowitz's avatar
      9e63d487
    • Jam Balaya's avatar
      chore(examples): remove `with-tigris` example (#81843) · 1ac8cb06
      Jam Balaya authored
      ## Summary
      
      Remove the
      [with-tigris](https://github.com/vercel/next.js/tree/canary/examples/with-tigris)
      example and clean up its references in lint and test configs
      
      Build:
      - Remove with-tigris paths from .eslintignore
      - Remove with-tigris entry from turbopack-dev-examples-manifest.json
      
      Chores:
      - Delete the with-tigris example directory and all its files
      
      ## Why?
      
      
      [@tigrisdata/core](https://github.com/tigrisdata-archive/tigris-client-ts)
      package hasn't been maintained in 2 years.
      
      ## Adding or Updating Examples
      
      - [x] The "examples guidelines" are followed from our contributing doc
      https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
      - [x] Make sure the linting passes by running `pnpm build && pnpm lint`.
      See
      https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md
      
      cc: @samcx
      Co-authored-by: 's avatarJoseph <joseph.chamochumbi@vercel.com>
      1ac8cb06
    • Niklas Mischkulnig's avatar
      37516d95
    • Andrew Clark's avatar
      Support MPA navigations in `instant()` (#89469) · 44ab1be4
      Andrew Clark authored
      Based on:
      
      - https://github.com/vercel/next.js/pull/89465
      
      ---
      
      The `instant()` testing API allows e2e tests to assert on prefetched UI
      before dynamic data streams in. This extends it to handle full page
      navigations: page reloads, plain anchor clicks, and browser
      back/forward.
      
      For client-side navigations, the API uses request headers to trigger
      static shell rendering. For MPA navigations, headers aren't available,
      so this uses a cookie-based approach instead. When `instant()` acquires
      a lock, it sets a cookie that tells the server to render the static
      shell. When the lock is released, the cookie is cleared and the page
      reloads to fetch dynamic content.
      
      On pages loaded with the test cookie, hydration is skipped entirely and
      a minimal testing API is set up in the bootstrap script. This is similar
      to how the `__nextppronly` debug parameter works (an internal experiment
      that was never shipped). This feature is the productionized version of
      that approach, designed for actual use in e2e tests.
      
      New test cases:
      - Static shell on page reload
      - Static shell on plain anchor navigation
      - Multiple MPA navigations within a single `instant()` scope
      - Verifies navigations work normally after exiting `instant()` scope
      44ab1be4
    • Andrew Clark's avatar
      Add Instant Navigation Testing API (#89465) · 5fbb9aa9
      Andrew Clark authored
      ## Summary
      
      Adds a dev-mode primitive for writing e2e tests that assert on the
      prefetched/cached portion of a navigation. The API blocks dynamic data
      from streaming in until assertions complete, allowing deterministic
      testing of loading states without race conditions.
      
      This gives developers a way to verify that specific UI elements render
      instantly from cache, rather than relying on network timing. It also
      reinforces the mental model that navigation performance should be
      thought of primarily in terms of cached vs. dynamic.
      
      This PR implements the primitive that Next.js exposes on the window
      object. In practice, it's meant to be used via a testing framework
      integration, like a Playwright helper:
      
      ```typescript
      await instant(page, async () => {
        await page.click('a[href="/products/123"]');
        await expect(page.locator('[data-testid="skeleton"]')).toBeVisible();
      });
      ```
      
      The implementation forces a prefetch before navigation when inside an
      `instant` scope (since prefetching is normally disabled in dev), then
      holds dynamic data until the scope ends. All code is wrapped in dev
      checks and gets dead code eliminated in production.
      
      Current scope is client-side navigations only. SSR/MPA support is
      planned as a follow-up.
      
      ## Test plan
      
      - `test/e2e/app-dir/instant-navigation-testing-api`
      5fbb9aa9
    • Tim Neutkens's avatar
      fix: use signal-based exit codes to prevent inspector blocking exit (#89351) · 178a4c71
      Tim Neutkens authored
      ## What?
      
      Use signal-based exit codes when shutting down the Next.js server to
      prevent the process from waiting for the debugger to disconnect.
      
      ## Why?
      
      When Node.js devtools are attached (via `--inspect` flag or the Next.js
      DevTools "Attach debugger" feature), pressing Ctrl+C causes the dev
      server to hang instead of exiting immediately. This happens because
      calling `process.exit(0)` makes Node.js treat it as a normal exit, which
      waits for all debuggers to disconnect before terminating.
      
      In contrast, plain Node.js terminates immediately on SIGINT even with a
      debugger attached, because signal-based termination doesn't wait for
      debuggers.
      
      ## How?
      
      Instead of calling `process.exit(0)` after cleanup, use signal-based
      exit codes:
      
      - SIGINT (signal 2) → `process.exit(130)` (128 + 2)
      - SIGTERM (signal 15) → `process.exit(143)` (128 + 15)
      
      This tells Node.js the process was terminated by a signal, which avoids
      the debugger wait behavior.
      
      Changes:
      - Modified the cleanup function to accept the signal that triggered it
      - Use `process.exit(signal === 'SIGINT' ? 130 : 143)` instead of
      `process.exit(0)`
      - Removed the previous `inspector.close()` workaround as it's no longer
      needed
      
      ---------
      Co-authored-by: 's avatarSebastian Sebbie Silbermann <sebastian.silbermann@vercel.com>
      178a4c71
    • Niklas Mischkulnig's avatar
      Add `experimental.reportSystemEnvInlining` for Turbopack (#89304) · 43136958
      Niklas Mischkulnig authored
      Part of PACK-6641
      
      We don't have a way to silence (ignore-comment) warnings
      And additionally, warnings in node_modules are always hidden...
      43136958
    • Vercel Release Bot's avatar
      Update Rspack development test manifest (#89424) · 1e474a41
      Vercel Release Bot authored
      This auto-generated PR updates the development integration test manifest used when testing Rspack.
      1e474a41
    • Vercel Release Bot's avatar
      Update Rspack production test manifest (#89423) · 5b2b59f3
      Vercel Release Bot authored
      This auto-generated PR updates the production integration test manifest used when testing Rspack.
      5b2b59f3
  3. 03 Feb, 2026 16 commits
  4. 02 Feb, 2026 8 commits