1. 11 Dec, 2025 4 commits
    • nextjs-bot's avatar
      v16.0.9 · 3f6a39f6
      nextjs-bot authored
      3f6a39f6
    • Josh Story's avatar
      Update React Versions (#40) · 75e136ad
      Josh Story authored
      75e136ad
    • Josh Story's avatar
      Update React Version (#22) · 4e20596a
      Josh Story authored
      4e20596a
    • Zack Tanner's avatar
      Backport Next.js changes to v16.0.9 (#20) · fa858489
      Zack Tanner authored
      * remove urlencoded server action handling (#14)
      
      * remove urlencoded server action handling
      
      * urlencoded POSTs should still flow through action handler
      
      * bailout early for urlencoded
      
      * tweak handling to 404 in feetch action case
      
      * error when there are no server actions (#15)
      
      * remove custom error
      
      * remove dev gate
      
      * error when there are no server actions
      
      * gate against dev
      
      * Check whether action ids are valid before parsing (#16)
      
      * Check whether action ids are valid before parsing
      
      In an effort to narrow access to parsing methods Next.js now prequalifies MPA form parsing by ensuring there are only valid action IDs as part of the submission. This is not meant to be a strong line of defense against malicious payloads since action IDs are not private and are for many apps relatively easy to acquire. It does however provide some limited narrowing of code paths so that action decoding only happens for plausible actions
      
      Additionally all other branches that use next-action header now consistently check the header before proceeding with parsing. This is also a perf improvement.
      
      * fix test assertion
      
      ---------
      Co-authored-by: 's avatarZack Tanner <1939140+ztanner@users.noreply.github.com>
      
      ---------
      Co-authored-by: 's avatarJosh Story <story@hey.com>
      fa858489
  2. 08 Dec, 2025 2 commits
  3. 03 Dec, 2025 3 commits
  4. 30 Nov, 2025 2 commits
  5. 26 Nov, 2025 2 commits
  6. 24 Nov, 2025 4 commits
  7. 13 Nov, 2025 2 commits
    • nextjs-bot's avatar
      v16.0.3 · 2eda33ce
      nextjs-bot authored
      2eda33ce
    • Jiachi Liu's avatar
      perf: revert to use the light safe stringify for is-error (#86053) · 00cb5d99
      Jiachi Liu authored
      `is-error` is a helper that being used accorss client and server now, in
      #84909 we switched the underlying safe stringify error implementation to
      the precompiled dependency `safe-stable-stringify`. But it increased the
      client bundle size a bit.
      
      The change in #84909 was only for applying the `safe-stable-stringify`
      for client file logger with mcp, not really necessary need to change for
      is-error helper
      
      Note: Save minified around 12kb. it's actually 7.5kb on bundlephobia,
      but because we're using ncc to compile it to cjs dependency that the
      size seems slightly larger than their metrics. The saved gzip size would
      be around 2-3.x kb
      00cb5d99
  8. 12 Nov, 2025 21 commits
    • Joseph's avatar
      docs: keywords in system reqs and add browserslist (#85838) · de6bc159
      Joseph authored
      Adding more searchable keywords
      de6bc159
    • Joseph's avatar
      docs: cacheHandlers (#85311) · a51b8044
      Joseph authored
      a51b8044
    • Niklas Mischkulnig's avatar
      a63951f4
    • Georges Farah's avatar
      Update authentication.mdx: Fix `Auth0` Link (#85953) · 8c29c118
      Georges Farah authored
      The `Auth0` link is broken so I fixed it
      
      <!-- Thanks for opening a PR! Your contribution is much appreciated.
      To make sure your PR is handled as smoothly as possible we request that
      you follow the checklist sections below.
      Choose the right checklist for the change(s) that you're making:
      
      ## For Contributors
      
      ### Improving Documentation
      
      - Run `pnpm prettier-fix` to fix formatting issues before opening the
      PR.
      - Read the Docs Contribution Guide to ensure your contribution follows
      the docs guidelines:
      https://nextjs.org/docs/community/contribution-guide
      
      ### Fixing a bug
      
      - Related issues linked using `fixes #number`
      - Tests added. See:
      https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
      - Errors have a helpful link attached, see
      https://github.com/vercel/next.js/blob/canary/contributing.md
      
      ### Adding a feature
      
      - Implements an existing feature request or RFC. Make sure the feature
      request has been accepted for implementation before opening a PR. (A
      discussion must be opened, see
      https://github.com/vercel/next.js/discussions/new?category=ideas)
      - Related issues/discussions are linked using `fixes #number`
      - e2e tests added
      (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
      - Documentation added
      - Telemetry added. In case of a feature if it's used or not.
      - Errors have a helpful link attached, see
      https://github.com/vercel/next.js/blob/canary/contributing.md
      
      
      ## For Maintainers
      
      - Minimal description (aim for explaining to someone not on the team to
      understand the PR)
      - When linking to a Slack thread, you might want to share details of the
      conclusion
      - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
      - Add review comments if necessary to explain to the reviewer the logic
      behind a change
      
      ### What?
      
      ### Why?
      
      ### How?
      
      Closes NEXT-
      Fixes #
      
      -->
      Co-authored-by: 's avatarJoseph <joseph.chamochumbi@vercel.com>
      8c29c118
    • James Daniels's avatar
      Deployment adapter: fix metadata for "/" route (#85820) · 25716c8e
      James Daniels authored
      Updates cases where `/` isn't normalized fully when interpolating into
      data paths and adds regression tests.
      
      ---------
      Co-authored-by: 's avatarvercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
      Co-authored-by: 's avatarJJ Kasper <jj@jjsweb.site>
      25716c8e
    • nextjs-bot's avatar
    • Zack Tanner's avatar
      switch to slice in createRuntimePrefetchTransformStream (#85822) · 4212a864
      Zack Tanner authored
      It's safer to copy here than to pass a reference, because it's possible
      that the underlying chunk became detached. Accidentally tweaked this
      before landing #85595
      4212a864
    • Shu Ding's avatar
      Fix Turbopack local font `font-family` declaration (#85913) · 07a86572
      Shu Ding authored
      This fixes #85912, as the logic of injecting the `font-family` property
      should be mirrored from the Webpack implementation.
      07a86572
    • Hendrik Liebau's avatar
    • Joseph's avatar
    • Hendrik Liebau's avatar
      Hoist inner `'use cache'` functions to reduce function allocations (#85904) · 822dcc7d
      Hendrik Liebau authored
      This PR fixes a slight performance regression introduced in #85519 where
      inline async function expressions were created for each unique set of
      arguments passed to a `'use cache'` function.
      
      For a function like this:
      
      ```js
      export async function getCachedData(id) {
        'use cache';
        return fetch(`/api/data/${id}`);
      }
      ```
      
      we were previously generating (simplified):
      
      ```js
      export var $$RSC_SERVER_CACHE_0 = cache("default", "0815", 0, async function(id) {
        return fetch(`/api/data/${id}`);
      });
      ```
      
      In #85519, we restructured this to ensure proper stack frames in error
      messages (simplified):
      
      ```js
      export var $$RSC_SERVER_CACHE_0 = React.cache(function getCachedData() {
        return cache("default", "0815", 0, async function(id) {
          return fetch(`/api/data/${id}`);
        }, arguments);
      });
      ```
      
      However, this introduced a small performance issue: the inner async
      function expression was passed inline to the cache wrapper. While
      `React.cache` memoizes the outer function, each unique set of arguments
      would cause a new inner function object to be allocated.
      
      Now we're generating (simplified):
      
      ```js
      const $$RSC_SERVER_CACHE_0_INNER = async function getCachedData(id) {
        return fetch(`/api/data/${id}`);
      };
      
      export var $$RSC_SERVER_CACHE_0 = React.cache(function getCachedData() {
        return cache("default", "0815", 0, $$RSC_SERVER_CACHE_0_INNER, arguments);
      });
      ```
      
      The cache implementation is now hoisted to module scope with an `_INNER`
      suffix as a const declaration with a named function expression. The
      function name is preserved to ensure proper stack traces in dev. This
      eliminates the repeated function allocations while preserving the
      improvements from #85519.
      822dcc7d
    • Hendrik Liebau's avatar
      [test] Increase response timeout in `next.browserWithResponse()` (#85911) · 499f5e19
      Hendrik Liebau authored
      The `next.browserWithResponse()` test helper is currently only used in
      the `fallback-shells` test suite, which frequently times out after 10
      seconds in CI, because the initial compilation for the first request can
      take quite a while when there's resource contention. Increasing the
      timeout to 30 seconds should help mitigate these issues. We could also
      consider removing the timeout entirely. Playwright also doesn't use a
      timeout per default for the `page.goto()` method, which we use for
      `next.browser()` and `next.browserWithResponse()` under the hood.
      499f5e19
    • Jude Gao's avatar
      Fix telemetry event loss on build failures and server shutdown (#85867) · 05f71f96
      Jude Gao authored
      ## Problem
      
      Telemetry events were not being captured in three scenarios:
      
      ### 1. MCP Telemetry Lost on Dev Server Shutdown
      
      Two telemetry instances were created during dev server startup. MCP
      events were recorded to one instance but shutdown flushed a different
      instance.
      
      **Fix:** Reuse the existing telemetry instance from `traceGlobals`.
      
      ### 2. Process Exit Timeout Killing Async Telemetry
      
      The CLI force-kills child processes after 100ms
      (`NEXT_EXIT_TIMEOUT_MS`). Async telemetry operations were interrupted
      before completion.
      
      **Fix:** Use `flushDetached()` to write events to disk and spawn a
      detached process for async submission, allowing immediate parent exit.
      
      ### 3. Build Errors Calling `process.exit()` Before Telemetry Flush
      
      `process.exit()` calls in error handlers (SWC failures, missing
      dependencies, route conflicts) bypassed finally blocks and killed
      processes before telemetry completed.
      
      **Fix:** Throw errors instead of calling `process.exit()`, add finally
      blocks with `await telemetry.flush()` in critical paths.
      
      ## Changes
      
      **Core:**
      - `server/dev/next-dev-server.ts`: Reuse telemetry instance
      - `server/lib/start-server.ts`: Use `flushDetached()` for shutdown
      - `build/swc/index.ts`: Remove `process.exit()` calls
      - `build/turbopack-build/impl.ts`: Add telemetry flush in worker finally
      block
      - `build/index.ts`: Add telemetry flush in finally block, throw instead
      of exit
      - `lib/verify-partytown-setup.ts`: Throw instead of exit
      
      **Supporting:**
      - `telemetry/storage.ts`: Generate unique event files per PID
      - `telemetry/detached-flush.ts`: Accept optional eventsFile parameter
      - `errors.json`: Update detached-flush error message
      
      ## Testing
      
      All telemetry tests now pass:
      - MCP telemetry on dev server shutdown
      - SWC load failures in worker threads
      - Build configuration errors
      
      ✅ Non-blocking shutdown  
      ✅ Timeout-independent  
      ✅ No race conditions  
      ✅ Works in worker threads
      05f71f96
    • nextjs-bot's avatar
    • Luke Sandberg's avatar
      [turbopack] Remove LocalTaskType::Native, it is dead (#85480) · f0fe0cb0
      Luke Sandberg authored
      ### What
      Remove `LocalTaskType::Native` and supporting infrastructure.  Simplify schedule_local_task to remove an allocation and `CaptureFuture`.
      
      ### Why?
      local tasks for things other than 'resolve' tasks have been proven to not be a very useful idea.  However, for resolve tasks they do still make sense.  We can use the small amount of indirection provided by `LocalTask` to optimize how we launch other turbotasks.
      
      Now that the local task implementation is clearly just about turbo-tasks infrastructure (rather than calling arbitrary 'user code') we can simplify dispatching a bit.
      f0fe0cb0
    • Luke Sandberg's avatar
      [turbopack] Make it possible to synchronously access native bindings (#85787) · 4b79b55b
      Luke Sandberg authored
      ## Enable synchronous access to native bindings
      
      ## What?
      This PR refactors the SWC bindings loading mechanism to support synchronous access to bindings after they've been loaded. It introduces new functions `installBindings()` and `getBindingsSync()` to properly manage the bindings lifecycle.
      
      `installBindings` is called early by tools that rely on them.
      
      There were of course  a few complexities:
      
      * webpack loaders need to defensively install bindings to support being run by webpack
      * the hacky `loadNativeSync` method used by `transformSync` remains required due to the jest-transformer API (i didn't see a clear initialization location).
      * the `experimental.useWasmBinary` configuration is broken by design
         * if the config is `next.config.ts` when we load SWC to transpile it, but that requires the native bindings, so we might load native bindings even when you ask for wasm.  I added a warning message for this case and the workaround is to use the node native transpilation support.
         * this should probably be a command line flag if it is important
      * we need to lazily load the `swc/index.ts` module since it transitively loads `react` which reads `NODE_ENV` and various next entrypoints might modify that.
      
      ## Why?
      
      This makes it clearer that we are correctly applying the `useWasmBinary` option and can simplify some code paths that now don't need to be `async`.  This will be important in a future PR where i move some parts of issue formatting into rust/wasm.  Having those APIs be async will decrease their usability.
      4b79b55b
    • Tessa's avatar
      Add Appwrite Sites to supported adapters (#85830) · 14a45e4d
      Tessa authored
      <!-- Thanks for opening a PR! Your contribution is much appreciated.
      To make sure your PR is handled as smoothly as possible we request that
      you follow the checklist sections below.
      Choose the right checklist for the change(s) that you're making:
      
      ## For Contributors
      
      ### Improving Documentation
      
      - Run `pnpm prettier-fix` to fix formatting issues before opening the
      PR.
      - Read the Docs Contribution Guide to ensure your contribution follows
      the docs guidelines:
      https://nextjs.org/docs/community/contribution-guide
      
      ### Fixing a bug
      
      - Related issues linked using `fixes #number`
      - Tests added. See:
      https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
      - Errors have a helpful link attached, see
      https://github.com/vercel/next.js/blob/canary/contributing.md
      
      ### Adding a feature
      
      - Implements an existing feature request or RFC. Make sure the feature
      request has been accepted for implementation before opening a PR. (A
      discussion must be opened, see
      https://github.com/vercel/next.js/discussions/new?category=ideas)
      - Related issues/discussions are linked using `fixes #number`
      - e2e tests added
      (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
      - Documentation added
      - Telemetry added. In case of a feature if it's used or not.
      - Errors have a helpful link attached, see
      https://github.com/vercel/next.js/blob/canary/contributing.md
      
      
      ## For Maintainers
      
      - Minimal description (aim for explaining to someone not on the team to
      understand the PR)
      - When linking to a Slack thread, you might want to share details of the
      conclusion
      - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
      - Add review comments if necessary to explain to the reviewer the logic
      behind a change
      
      ### What?
      
      Added Appwrite Sites to the list of deployment adapters in the deploying
      documentation.
      
      ### Why?
      
      Appwrite Sites is a deployment platform that uses an adapter to run
      Next.js applications on their infrastructure, similar to other platforms
      listed in the Adapters section (Cloudflare, Netlify, AWS Amplify, etc.).
      This addition helps developers discover Appwrite Sites as a deployment
      option for their Next.js applications.
      
      ### How?
      
      Added a link to Appwrite Sites documentation
      (https://appwrite.io/docs/products/sites/quick-start/nextjs in the
      Adapters section of 17-deploying.mdx
      
      Closes NEXT-
      Fixes #
      
      -->
      
      ### What?
      
      Added Appwrite Sites to the list of deployment adapters in the deploying
      documentation.
      
      ### Why?
      
      Appwrite Sites is a deployment platform that uses an adapter to run
      Next.js applications on their infrastructure, similar to other platforms
      listed in the Adapters section (Cloudflare, Netlify, AWS Amplify, etc.).
      This addition helps developers discover Appwrite Sites as a deployment
      option for their Next.js applications.
      
      ### How?
      
      Added a link to Appwrite Sites documentation
      (https://appwrite.io/docs/products/sites/quick-start/nextjs in the
      Adapters section of 17-deploying.mdx
      14a45e4d
    • Tobias Koppers's avatar
      Turbopack: Fix IO concurrency for MacOS (#85861) · 9cc4f33c
      Tobias Koppers authored
      ### What?
      
      The previous default of 256 parallel write operations caused a serious performance problem. For a bigger application this change improves write performance by 5.8x (12.8s -> 2.2s) on MacOS.
      9cc4f33c
    • Benjamin Woodruff's avatar
      Turbopack: chore: Merge `turbo-tasks-macros-shared` crate into `turbo-tasks-macros` (#85917) · 1a80404b
      Benjamin Woodruff authored
      This was left over from the `turbo-tasks-build` crate, which @lukesandberg eliminated in favor of `inventory`. This crate was used for sharing code between `turbo-tasks-build` and `turbo-tasks-macros`.
      
      We can just merge these crates together now.
      
      Regarding compilation time: The dependency graph here is pretty linear, so I don't think there's any benefit from splitting these.
      1a80404b
    • JJ Kasper's avatar
      Update deploy manifest (#85924) · c601ffe3
      JJ Kasper authored
      The filter condition on the existing tests was incorrect so updated
      those and added flakey prefetch ones from
      
      
      https://github.com/vercel/next.js/actions/runs/19184159066/job/54847336252
      
      https://github.com/vercel/next.js/actions/runs/19184159066/job/54847336291
      c601ffe3
    • Vercel Release Bot's avatar
      Update font data (#85920) · bd08f17f
      Vercel Release Bot authored
      This auto-generated PR updates font data with latest available
      Co-authored-by: 's avatarnextjs-bot <it+nextjs-bot@vercel.com>
      bd08f17f