Search results

App crashes on POST requests with <code>Origin: null</code> + <code>Content-Type: application/x-www-form-urlencoded</code> headers

Error HandlingRelated to handling errors (e.g., error.tsx, global-error.tsx).Related to handling errors (e.g., error.tsx, global-error.tsx).

HeadersRelated to the async headers() function.Related to the async headers() function.

Status: Open.

Bug

#84786 In vercel/next.js;

· a9ex opened on Oct 12, 2025

Aborted requests cause middleware to crash in development

Error HandlingRelated to handling errors (e.g., error.tsx, global-error.tsx).Related to handling errors (e.g., error.tsx, global-error.tsx).

Route HandlersRelated to Route Handlers.Related to Route Handlers.

TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.

WebpackRelated to Webpack with Next.js.Related to Webpack with Next.js.

Status: Open.

Bug

#84649 In vercel/next.js;

· alex-statsig opened on Oct 8, 2025

Logging an <code>AggregateError</code> doesn't include the <code>[errors]</code> section.

Error HandlingRelated to handling errors (e.g., error.tsx, global-error.tsx).Related to handling errors (e.g., error.tsx, global-error.tsx).

Route HandlersRelated to Route Handlers.Related to Route Handlers.

Status: Open.

Bug

#84464 In vercel/next.js;

· bencmbrook opened on Oct 2, 2025

onRequestError is not triggered for middleware when runtime is nodejs

Error HandlingRelated to handling errors (e.g., error.tsx, global-error.tsx).Related to handling errors (e.g., error.tsx, global-error.tsx).

Status: Open.

Bug

#84181 In vercel/next.js;

· yiminghe opened on Sep 24, 2025

Scripts with beforeInteractive are no executed when server response is not 200

Error HandlingRelated to handling errors (e.g., error.tsx, global-error.tsx).Related to handling errors (e.g., error.tsx, global-error.tsx).

Not FoundRelated to the not-found.tsx file or the notFound() function.Related to the not-found.tsx file or the notFound() function.

Script (next/script)Related to Next.js Script Optimization.Related to Next.js Script Optimization.

Status: Open.

Bug

#83326 In vercel/next.js;

· gavroman opened on Sep 2, 2025

Inline script from layout doesn't run on not found page when using parallel routes

Error HandlingRelated to handling errors (e.g., error.tsx, global-error.tsx).Related to handling errors (e.g., error.tsx, global-error.tsx).

Not FoundRelated to the not-found.tsx file or the notFound() function.Related to the not-found.tsx file or the notFound() function.

Parallel & Intercepting RoutesRelated to Parallel and/or Intercepting routes.Related to Parallel and/or Intercepting routes.

Status: Open.

Bug

#82456 In vercel/next.js;

· dmitrc opened on Aug 8, 2025

Missing &lt;html&gt; and &lt;body&gt; tags in the root layout with multiple root layout

Dynamic RoutesRelated to dynamic routes.Related to dynamic routes.

Error HandlingRelated to handling errors (e.g., error.tsx, global-error.tsx).Related to handling errors (e.g., error.tsx, global-error.tsx).

Internationalization (i18n)Related to Internationalization with Next.js.Related to Internationalization with Next.js.

Not FoundRelated to the not-found.tsx file or the notFound() function.Related to the not-found.tsx file or the notFound() function.

Route HandlersRelated to Route Handlers.Related to Route Handlers.

Status: Open.

Bug

#82446 In vercel/next.js;

· mjy9088 opened on Aug 7, 2025

Navigation incorrectly redirects to .txt file showing RSC payload when prefetch/router methods fail

Error HandlingRelated to handling errors (e.g., error.tsx, global-error.tsx).Related to handling errors (e.g., error.tsx, global-error.tsx).

Status: Open.

Bug

#82417 In vercel/next.js;

· azu opened on Aug 6, 2025

Custom 404 in pages router not work as expected when using both pages router and app router

Error HandlingRelated to handling errors (e.g., error.tsx, global-error.tsx).Related to handling errors (e.g., error.tsx, global-error.tsx).

Pages RouterRelated to Pages Router.Related to Pages Router.

Status: Open.

Bug

#82229 In vercel/next.js;

· yunsii opened on Jul 31, 2025

Incorrect HTTP error status codes from non-streaming generateMetadata

Error HandlingRelated to handling errors (e.g., error.tsx, global-error.tsx).Related to handling errors (e.g., error.tsx, global-error.tsx).

Status: Open.

Bug

#82041 In vercel/next.js;

· p00000001 opened on Jul 25, 2025

[next-devtools] <code>experimental.browserDebugInTerminal</code> flag not showing source locations

Error HandlingRelated to handling errors (e.g., error.tsx, global-error.tsx).Related to handling errors (e.g., error.tsx, global-error.tsx).

linear: turbopackConfirmed issue that is tracked by the Turbopack team.Confirmed issue that is tracked by the Turbopack team.

RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.

TestingRelated to testing with Next.js.Related to testing with Next.js.

TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.

Status: Open.

Bug

#81498 In vercel/next.js;

· PlagueFPS opened on Jul 10, 2025

Calling notFound() on a page that is force-static gets cached

Error HandlingRelated to handling errors (e.g., error.tsx, global-error.tsx).Related to handling errors (e.g., error.tsx, global-error.tsx).

HeadersRelated to the async headers() function.Related to the async headers() function.

Status: Open.

Bug

#81290 In vercel/next.js;

· yoohahn opened on Jul 4, 2025