vinext 0.0.51 → 0.0.53

package/dist/server/pages-api-route.d.ts

@@ -1,9 +1,45 @@
 import { Route } from "../routing/pages-router.js";
+import { ExecutionContextLike } from "../shims/request-context.js";
 import { PagesReqResRequest, PagesReqResResponse, PagesRequestQuery } from "./pages-node-compat.js";
 
 //#region src/server/pages-api-route.d.ts
+type PagesApiRouteConfig = {
+  runtime?: string;
+  /**
+   * `export const config = { api: { bodyParser: false | { sizeLimit: '4mb' } } }`
+   * — controls whether vinext parses the request body for the route handler.
+   *
+   * `bodyParser: false` is critical for webhook handlers (Stripe, GitHub,
+   * Slack, etc.) that need to read the raw bytes to verify an HMAC
+   * signature. With it set, `req.body` is left undefined and the raw stream
+   * is exposed on `req.body` as a Web `ReadableStream<Uint8Array>` so user
+   * code can consume it.
+   *
+   * @see https://nextjs.org/docs/pages/building-your-application/routing/api-routes#custom-config
+   */
+  api?: {
+    bodyParser?: boolean | {
+      sizeLimit?: string | number;
+    };
+    responseLimit?: boolean | string | number;
+  };
+};
+type PagesNodeApiRouteHandler = (req: PagesReqResRequest, res: PagesReqResResponse) => void | Promise<void>;
+type PagesEdgeApiRouteHandler = (request: Request) => Response | Promise<Response>;
 type PagesApiRouteModule = {
-  default?: (req: PagesReqResRequest, res: PagesReqResResponse) => void | Promise<void>;
+  /**
+   * `export const config = { runtime: 'edge' }` — historical Pages Router form.
+   */
+  config?: PagesApiRouteConfig;
+  /**
+   * `export const runtime = 'edge'` — bare export form. Next.js resolves the
+   * effective runtime as `config.runtime ?? config.config?.runtime`, so a
+   * top-level `runtime` export takes precedence over the nested config form.
+   *
+   * @see https://github.com/vercel/next.js/blob/canary/packages/next/src/build/analysis/get-page-static-info.ts
+   */
+  runtime?: string;
+  default?: PagesNodeApiRouteHandler | PagesEdgeApiRouteHandler;
 };
 type PagesApiRouteMatch = {
   params: PagesRequestQuery;
@@ -12,6 +48,14 @@ type PagesApiRouteMatch = {
   };
 };
 type HandlePagesApiRouteOptions = {
+  /**
+   * Per-request Cloudflare Workers `ExecutionContext`. When provided, the
+   * API route runs inside `runWithExecutionContext(ctx, ...)` so any
+   * `after()` (or other shim) call inside the handler can reach
+   * `ctx.waitUntil()` via the ALS and keep the isolate alive past the
+   * response. Omit on Node.js dev where no Workers lifecycle exists.
+   */
+  ctx?: ExecutionContextLike;
   match: PagesApiRouteMatch | null;
   reportRequestError?: (error: Error, routePattern: string) => void | Promise<void>;
   request: Request;

package/dist/server/pages-api-route.js

@@ -1,26 +1,49 @@
 import "./server-globals.js";
+import { runWithExecutionContext } from "../shims/request-context.js";
+import { NextRequest } from "../shims/server.js";
 import { internalServerErrorResponse } from "./http-error-responses.js";
 import { mergeRouteParamsIntoQuery, parseQueryString } from "../utils/query.js";
 import { PagesBodyParseError } from "./pages-media-type.js";
+import { isEdgeApiRuntime } from "./edge-api-runtime.js";
+import { resolveBodyParserConfig } from "./pages-body-parser-config.js";
 import { createPagesReqRes, parsePagesApiBody } from "./pages-node-compat.js";
 //#region src/server/pages-api-route.ts
+function resolveModuleRuntime(module) {
+	return module.runtime ?? module.config?.runtime;
+}
 function buildPagesApiQuery(url, params) {
 	return mergeRouteParamsIntoQuery(parseQueryString(url), params);
 }
+function isEdgeApiRouteModule(module) {
+	return typeof module.default === "function" && isEdgeApiRuntime(resolveModuleRuntime(module));
+}
+function isNodeApiRouteModule(module) {
+	return typeof module.default === "function" && !isEdgeApiRuntime(resolveModuleRuntime(module));
+}
 async function handlePagesApiRoute(options) {
+	if (options.ctx) return runWithExecutionContext(options.ctx, () => _handlePagesApiRoute(options));
+	return _handlePagesApiRoute(options);
+}
+async function _handlePagesApiRoute(options) {
 	if (!options.match) return new Response("404 - API route not found", { status: 404 });
 	const { route, params } = options.match;
-	const handler = route.module.default;
-	if (typeof handler !== "function") return new Response("API route does not export a default function", { status: 500 });
 	try {
+		if (isEdgeApiRouteModule(route.module)) {
+			const nextRequest = new NextRequest(options.request);
+			const response = await route.module.default(nextRequest);
+			if (response instanceof Response) return response;
+			throw new Error("Edge API route did not return a Response");
+		}
+		if (!isNodeApiRouteModule(route.module)) return new Response("API route does not export a default function", { status: 500 });
 		const query = buildPagesApiQuery(options.url, params);
+		const bodyParserConfig = resolveBodyParserConfig(route.module.config);
 		const { req, res, responsePromise } = createPagesReqRes({
-			body: await parsePagesApiBody(options.request),
+			body: bodyParserConfig.enabled ? await parsePagesApiBody(options.request, bodyParserConfig.sizeLimit) : options.request.body ?? void 0,
 			query,
 			request: options.request,
 			url: options.url
 		});
-		await handler(req, res);
+		await route.module.default(req, res);
 		res.end();
 		return await responsePromise;
 	} catch (error) {

package/dist/server/pages-api-route.js.map

@@ -1 +1 @@
-{"version":3,"file":"pages-api-route.js","names":["PagesApiBodyParseError"],"sources":["../../src/server/pages-api-route.ts"],"sourcesContent":["import \"./server-globals.js\";\nimport type { Route } from \"../routing/pages-router.js\";\nimport { mergeRouteParamsIntoQuery, parseQueryString } from \"../utils/query.js\";\nimport {\n  createPagesReqRes,\n  parsePagesApiBody,\n  type PagesRequestQuery,\n  type PagesReqResRequest,\n  type PagesReqResResponse,\n  PagesApiBodyParseError,\n} from \"./pages-node-compat.js\";\nimport { internalServerErrorResponse } from \"./http-error-responses.js\";\n\ntype PagesApiRouteModule = {\n  default?: (req: PagesReqResRequest, res: PagesReqResResponse) => void | Promise<void>;\n};\n\nexport type PagesApiRouteMatch = {\n  params: PagesRequestQuery;\n  route: Pick<Route, \"pattern\"> & {\n    module: PagesApiRouteModule;\n  };\n};\n\ntype HandlePagesApiRouteOptions = {\n  match: PagesApiRouteMatch | null;\n  reportRequestError?: (error: Error, routePattern: string) => void | Promise<void>;\n  request: Request;\n  url: string;\n};\n\nfunction buildPagesApiQuery(url: string, params: PagesRequestQuery): PagesRequestQuery {\n  return mergeRouteParamsIntoQuery(parseQueryString(url), params);\n}\n\nexport async function handlePagesApiRoute(options: HandlePagesApiRouteOptions): Promise<Response> {\n  if (!options.match) {\n    return new Response(\"404 - API route not found\", { status: 404 });\n  }\n\n  const { route, params } = options.match;\n  const handler = route.module.default;\n  if (typeof handler !== \"function\") {\n    return new Response(\"API route does not export a default function\", { status: 500 });\n  }\n\n  try {\n    const query = buildPagesApiQuery(options.url, params);\n    const body = await parsePagesApiBody(options.request);\n    const { req, res, responsePromise } = createPagesReqRes({\n      body,\n      query,\n      request: options.request,\n      url: options.url,\n    });\n\n    await handler(req, res);\n    res.end();\n    return await responsePromise;\n  } catch (error) {\n    if (error instanceof PagesApiBodyParseError) {\n      return new Response(error.message, {\n        status: error.statusCode,\n        statusText: error.message,\n      });\n    }\n\n    void options.reportRequestError?.(\n      error instanceof Error ? error : new Error(String(error)),\n      route.pattern,\n    );\n    return internalServerErrorResponse();\n  }\n}\n"],"mappings":";;;;;;AA+BA,SAAS,mBAAmB,KAAa,QAA8C;CACrF,OAAO,0BAA0B,iBAAiB,IAAI,EAAE,OAAO;;AAGjE,eAAsB,oBAAoB,SAAwD;CAChG,IAAI,CAAC,QAAQ,OACX,OAAO,IAAI,SAAS,6BAA6B,EAAE,QAAQ,KAAK,CAAC;CAGnE,MAAM,EAAE,OAAO,WAAW,QAAQ;CAClC,MAAM,UAAU,MAAM,OAAO;CAC7B,IAAI,OAAO,YAAY,YACrB,OAAO,IAAI,SAAS,gDAAgD,EAAE,QAAQ,KAAK,CAAC;CAGtF,IAAI;EACF,MAAM,QAAQ,mBAAmB,QAAQ,KAAK,OAAO;EAErD,MAAM,EAAE,KAAK,KAAK,oBAAoB,kBAAkB;GACtD,MAAA,MAFiB,kBAAkB,QAAQ,QAAQ;GAGnD;GACA,SAAS,QAAQ;GACjB,KAAK,QAAQ;GACd,CAAC;EAEF,MAAM,QAAQ,KAAK,IAAI;EACvB,IAAI,KAAK;EACT,OAAO,MAAM;UACN,OAAO;EACd,IAAI,iBAAiBA,qBACnB,OAAO,IAAI,SAAS,MAAM,SAAS;GACjC,QAAQ,MAAM;GACd,YAAY,MAAM;GACnB,CAAC;EAGJ,QAAa,qBACX,iBAAiB,QAAQ,QAAQ,IAAI,MAAM,OAAO,MAAM,CAAC,EACzD,MAAM,QACP;EACD,OAAO,6BAA6B"}
+{"version":3,"file":"pages-api-route.js","names":["PagesApiBodyParseError"],"sources":["../../src/server/pages-api-route.ts"],"sourcesContent":["import \"./server-globals.js\";\nimport type { Route } from \"../routing/pages-router.js\";\nimport { mergeRouteParamsIntoQuery, parseQueryString } from \"../utils/query.js\";\nimport {\n  createPagesReqRes,\n  parsePagesApiBody,\n  type PagesRequestQuery,\n  type PagesReqResRequest,\n  type PagesReqResResponse,\n  PagesApiBodyParseError,\n} from \"./pages-node-compat.js\";\nimport { resolveBodyParserConfig } from \"./pages-body-parser-config.js\";\nimport { internalServerErrorResponse } from \"./http-error-responses.js\";\nimport { isEdgeApiRuntime } from \"./edge-api-runtime.js\";\nimport { runWithExecutionContext, type ExecutionContextLike } from \"vinext/shims/request-context\";\nimport { NextRequest } from \"vinext/shims/server\";\n\ntype PagesApiRouteConfig = {\n  runtime?: string;\n  /**\n   * `export const config = { api: { bodyParser: false | { sizeLimit: '4mb' } } }`\n   * — controls whether vinext parses the request body for the route handler.\n   *\n   * `bodyParser: false` is critical for webhook handlers (Stripe, GitHub,\n   * Slack, etc.) that need to read the raw bytes to verify an HMAC\n   * signature. With it set, `req.body` is left undefined and the raw stream\n   * is exposed on `req.body` as a Web `ReadableStream<Uint8Array>` so user\n   * code can consume it.\n   *\n   * @see https://nextjs.org/docs/pages/building-your-application/routing/api-routes#custom-config\n   */\n  api?: {\n    bodyParser?: boolean | { sizeLimit?: string | number };\n    responseLimit?: boolean | string | number;\n  };\n};\n\ntype PagesNodeApiRouteHandler = (\n  req: PagesReqResRequest,\n  res: PagesReqResResponse,\n) => void | Promise<void>;\n\ntype PagesEdgeApiRouteHandler = (request: Request) => Response | Promise<Response>;\n\ntype PagesApiRouteModule = {\n  /**\n   * `export const config = { runtime: 'edge' }` — historical Pages Router form.\n   */\n  config?: PagesApiRouteConfig;\n  /**\n   * `export const runtime = 'edge'` — bare export form. Next.js resolves the\n   * effective runtime as `config.runtime ?? config.config?.runtime`, so a\n   * top-level `runtime` export takes precedence over the nested config form.\n   *\n   * @see https://github.com/vercel/next.js/blob/canary/packages/next/src/build/analysis/get-page-static-info.ts\n   */\n  runtime?: string;\n  default?: PagesNodeApiRouteHandler | PagesEdgeApiRouteHandler;\n};\n\nfunction resolveModuleRuntime(module: PagesApiRouteModule): string | undefined {\n  return module.runtime ?? module.config?.runtime;\n}\n\nexport type PagesApiRouteMatch = {\n  params: PagesRequestQuery;\n  route: Pick<Route, \"pattern\"> & {\n    module: PagesApiRouteModule;\n  };\n};\n\ntype HandlePagesApiRouteOptions = {\n  /**\n   * Per-request Cloudflare Workers `ExecutionContext`. When provided, the\n   * API route runs inside `runWithExecutionContext(ctx, ...)` so any\n   * `after()` (or other shim) call inside the handler can reach\n   * `ctx.waitUntil()` via the ALS and keep the isolate alive past the\n   * response. Omit on Node.js dev where no Workers lifecycle exists.\n   */\n  ctx?: ExecutionContextLike;\n  match: PagesApiRouteMatch | null;\n  reportRequestError?: (error: Error, routePattern: string) => void | Promise<void>;\n  request: Request;\n  url: string;\n};\n\nfunction buildPagesApiQuery(url: string, params: PagesRequestQuery): PagesRequestQuery {\n  return mergeRouteParamsIntoQuery(parseQueryString(url), params);\n}\n\nfunction isEdgeApiRouteModule(\n  module: PagesApiRouteModule,\n): module is PagesApiRouteModule & { default: PagesEdgeApiRouteHandler } {\n  return typeof module.default === \"function\" && isEdgeApiRuntime(resolveModuleRuntime(module));\n}\n\nfunction isNodeApiRouteModule(\n  module: PagesApiRouteModule,\n): module is PagesApiRouteModule & { default: PagesNodeApiRouteHandler } {\n  return typeof module.default === \"function\" && !isEdgeApiRuntime(resolveModuleRuntime(module));\n}\n\nexport async function handlePagesApiRoute(options: HandlePagesApiRouteOptions): Promise<Response> {\n  if (options.ctx) {\n    return runWithExecutionContext(options.ctx, () => _handlePagesApiRoute(options));\n  }\n  return _handlePagesApiRoute(options);\n}\n\nasync function _handlePagesApiRoute(options: HandlePagesApiRouteOptions): Promise<Response> {\n  if (!options.match) {\n    return new Response(\"404 - API route not found\", { status: 404 });\n  }\n\n  const { route, params } = options.match;\n\n  try {\n    if (isEdgeApiRouteModule(route.module)) {\n      // Next.js wraps the incoming Request in a NextRequest before invoking\n      // edge API handlers, so handlers can use `req.nextUrl.searchParams`,\n      // `req.cookies`, etc. (Cf. NextRequestHint in next/src/server/web/adapter.ts.)\n      const nextRequest = new NextRequest(options.request);\n      const response = await route.module.default(nextRequest);\n      if (response instanceof Response) {\n        return response;\n      }\n\n      throw new Error(\"Edge API route did not return a Response\");\n    }\n\n    // This is redundant at runtime after the edge branch for function exports, but it\n    // keeps the Node handler ABI narrowed without a production type assertion.\n    if (!isNodeApiRouteModule(route.module)) {\n      return new Response(\"API route does not export a default function\", { status: 500 });\n    }\n\n    const query = buildPagesApiQuery(options.url, params);\n\n    // Honour `export const config = { api: { bodyParser: ... } }` on the\n    // route module. When the handler opts out (`bodyParser: false`) we must\n    // not consume the stream — leave `req.body` as the raw Web\n    // `ReadableStream<Uint8Array>` so user code (e.g. a Stripe/GitHub\n    // webhook) can read the raw bytes for HMAC verification.\n    const bodyParserConfig = resolveBodyParserConfig(route.module.config);\n\n    const body = bodyParserConfig.enabled\n      ? await parsePagesApiBody(options.request, bodyParserConfig.sizeLimit)\n      : (options.request.body ?? undefined);\n\n    const { req, res, responsePromise } = createPagesReqRes({\n      body,\n      query,\n      request: options.request,\n      url: options.url,\n    });\n\n    await route.module.default(req, res);\n    res.end();\n    return await responsePromise;\n  } catch (error) {\n    if (error instanceof PagesApiBodyParseError) {\n      return new Response(error.message, {\n        status: error.statusCode,\n        statusText: error.message,\n      });\n    }\n\n    void options.reportRequestError?.(\n      error instanceof Error ? error : new Error(String(error)),\n      route.pattern,\n    );\n    return internalServerErrorResponse();\n  }\n}\n"],"mappings":";;;;;;;;;;AA4DA,SAAS,qBAAqB,QAAiD;CAC7E,OAAO,OAAO,WAAW,OAAO,QAAQ;;AAyB1C,SAAS,mBAAmB,KAAa,QAA8C;CACrF,OAAO,0BAA0B,iBAAiB,IAAI,EAAE,OAAO;;AAGjE,SAAS,qBACP,QACuE;CACvE,OAAO,OAAO,OAAO,YAAY,cAAc,iBAAiB,qBAAqB,OAAO,CAAC;;AAG/F,SAAS,qBACP,QACuE;CACvE,OAAO,OAAO,OAAO,YAAY,cAAc,CAAC,iBAAiB,qBAAqB,OAAO,CAAC;;AAGhG,eAAsB,oBAAoB,SAAwD;CAChG,IAAI,QAAQ,KACV,OAAO,wBAAwB,QAAQ,WAAW,qBAAqB,QAAQ,CAAC;CAElF,OAAO,qBAAqB,QAAQ;;AAGtC,eAAe,qBAAqB,SAAwD;CAC1F,IAAI,CAAC,QAAQ,OACX,OAAO,IAAI,SAAS,6BAA6B,EAAE,QAAQ,KAAK,CAAC;CAGnE,MAAM,EAAE,OAAO,WAAW,QAAQ;CAElC,IAAI;EACF,IAAI,qBAAqB,MAAM,OAAO,EAAE;GAItC,MAAM,cAAc,IAAI,YAAY,QAAQ,QAAQ;GACpD,MAAM,WAAW,MAAM,MAAM,OAAO,QAAQ,YAAY;GACxD,IAAI,oBAAoB,UACtB,OAAO;GAGT,MAAM,IAAI,MAAM,2CAA2C;;EAK7D,IAAI,CAAC,qBAAqB,MAAM,OAAO,EACrC,OAAO,IAAI,SAAS,gDAAgD,EAAE,QAAQ,KAAK,CAAC;EAGtF,MAAM,QAAQ,mBAAmB,QAAQ,KAAK,OAAO;EAOrD,MAAM,mBAAmB,wBAAwB,MAAM,OAAO,OAAO;EAMrE,MAAM,EAAE,KAAK,KAAK,oBAAoB,kBAAkB;GACtD,MALW,iBAAiB,UAC1B,MAAM,kBAAkB,QAAQ,SAAS,iBAAiB,UAAU,GACnE,QAAQ,QAAQ,QAAQ,KAAA;GAI3B;GACA,SAAS,QAAQ;GACjB,KAAK,QAAQ;GACd,CAAC;EAEF,MAAM,MAAM,OAAO,QAAQ,KAAK,IAAI;EACpC,IAAI,KAAK;EACT,OAAO,MAAM;UACN,OAAO;EACd,IAAI,iBAAiBA,qBACnB,OAAO,IAAI,SAAS,MAAM,SAAS;GACjC,QAAQ,MAAM;GACd,YAAY,MAAM;GACnB,CAAC;EAGJ,QAAa,qBACX,iBAAiB,QAAQ,QAAQ,IAAI,MAAM,OAAO,MAAM,CAAC,EACzD,MAAM,QACP;EACD,OAAO,6BAA6B"}

package/dist/server/pages-body-parser-config.d.ts

@@ -0,0 +1,60 @@
+//#region src/server/pages-body-parser-config.d.ts
+/**
+ * Resolve the Pages Router `api.bodyParser` config from a route module export.
+ *
+ * Next.js API routes can opt out of automatic body parsing or raise the
+ * default 1 MB size limit:
+ *
+ *   export const config = { api: { bodyParser: false } };
+ *   export const config = { api: { bodyParser: { sizeLimit: '4mb' } } };
+ *
+ * `bodyParser: false` is critical for webhook handlers (Stripe, GitHub,
+ * Slack, etc.) that must read the raw request bytes to verify an HMAC
+ * signature. Silently parsing the body would consume the stream and break
+ * signature verification — usually failing closed, sometimes failing open.
+ *
+ * @see https://nextjs.org/docs/pages/building-your-application/routing/api-routes#custom-config
+ * @see Next.js: packages/next/src/server/api-utils/node/api-resolver.ts
+ *
+ * The format of `sizeLimit` mirrors what Next.js accepts via the `bytes`
+ * package: a number of bytes, or a string with a unit suffix
+ * (`"500b"`, `"100kb"`, `"4mb"`, `"1gb"`).
+ */
+/**
+ * Default Pages Router API body size limit, matching Next.js.
+ */
+declare const DEFAULT_PAGES_API_BODY_SIZE_LIMIT: number;
+/**
+ * Resolved bodyParser configuration. When `enabled` is `false`, the body
+ * MUST be passed through to the handler as a raw stream (or left unparsed
+ * with `req.body === undefined`), so user code can read it itself.
+ */
+type ResolvedBodyParserConfig = {
+  enabled: false;
+} | {
+  enabled: true;
+  sizeLimit: number;
+};
+/**
+ * Parse a Next.js-style `sizeLimit` string (e.g. `"4mb"`, `"100kb"`, `"1gb"`)
+ * or numeric byte value into a number of bytes. Returns `undefined` for
+ * inputs that can't be parsed — callers should fall back to the default.
+ *
+ * Matches the format accepted by Next.js (the `bytes` package); we
+ * implement it inline to avoid pulling a dependency for a tiny parser.
+ */
+declare function parseSizeLimit(value: string | number | undefined): number | undefined;
+/**
+ * Read the resolved `bodyParser` config from a route module's `config`
+ * export. Defaults to enabled with the 1 MB Next.js default.
+ */
+declare function resolveBodyParserConfig(moduleConfig: {
+  api?: {
+    bodyParser?: boolean | {
+      sizeLimit?: string | number;
+    };
+  };
+} | undefined, defaultSizeLimit?: number): ResolvedBodyParserConfig;
+//#endregion
+export { DEFAULT_PAGES_API_BODY_SIZE_LIMIT, parseSizeLimit, resolveBodyParserConfig };
+//# sourceMappingURL=pages-body-parser-config.d.ts.map

package/dist/server/pages-body-parser-config.js

@@ -0,0 +1,79 @@
+//#region src/server/pages-body-parser-config.ts
+/**
+* Resolve the Pages Router `api.bodyParser` config from a route module export.
+*
+* Next.js API routes can opt out of automatic body parsing or raise the
+* default 1 MB size limit:
+*
+*   export const config = { api: { bodyParser: false } };
+*   export const config = { api: { bodyParser: { sizeLimit: '4mb' } } };
+*
+* `bodyParser: false` is critical for webhook handlers (Stripe, GitHub,
+* Slack, etc.) that must read the raw request bytes to verify an HMAC
+* signature. Silently parsing the body would consume the stream and break
+* signature verification — usually failing closed, sometimes failing open.
+*
+* @see https://nextjs.org/docs/pages/building-your-application/routing/api-routes#custom-config
+* @see Next.js: packages/next/src/server/api-utils/node/api-resolver.ts
+*
+* The format of `sizeLimit` mirrors what Next.js accepts via the `bytes`
+* package: a number of bytes, or a string with a unit suffix
+* (`"500b"`, `"100kb"`, `"4mb"`, `"1gb"`).
+*/
+/**
+* Default Pages Router API body size limit, matching Next.js.
+*/
+const DEFAULT_PAGES_API_BODY_SIZE_LIMIT = 1 * 1024 * 1024;
+const SIZE_UNITS = {
+	b: 1,
+	kb: 1024,
+	mb: 1024 * 1024,
+	gb: 1024 * 1024 * 1024,
+	tb: 1024 * 1024 * 1024 * 1024
+};
+/**
+* Parse a Next.js-style `sizeLimit` string (e.g. `"4mb"`, `"100kb"`, `"1gb"`)
+* or numeric byte value into a number of bytes. Returns `undefined` for
+* inputs that can't be parsed — callers should fall back to the default.
+*
+* Matches the format accepted by Next.js (the `bytes` package); we
+* implement it inline to avoid pulling a dependency for a tiny parser.
+*/
+function parseSizeLimit(value) {
+	if (value === void 0 || value === null) return void 0;
+	if (typeof value === "number") return Number.isFinite(value) && value >= 0 ? value : void 0;
+	if (typeof value !== "string") return void 0;
+	const trimmed = value.trim().toLowerCase();
+	if (!trimmed) return void 0;
+	const match = /^(\d+(?:\.\d+)?)\s*(b|kb|mb|gb|tb)?$/.exec(trimmed);
+	if (!match) return void 0;
+	const amount = Number.parseFloat(match[1]);
+	if (!Number.isFinite(amount) || amount < 0) return void 0;
+	const multiplier = SIZE_UNITS[match[2] ?? "b"];
+	if (multiplier === void 0) return void 0;
+	return Math.floor(amount * multiplier);
+}
+/**
+* Read the resolved `bodyParser` config from a route module's `config`
+* export. Defaults to enabled with the 1 MB Next.js default.
+*/
+function resolveBodyParserConfig(moduleConfig, defaultSizeLimit = DEFAULT_PAGES_API_BODY_SIZE_LIMIT) {
+	const bodyParser = moduleConfig?.api?.bodyParser;
+	if (bodyParser === false) return { enabled: false };
+	if (bodyParser === void 0 || bodyParser === true) return {
+		enabled: true,
+		sizeLimit: defaultSizeLimit
+	};
+	if (typeof bodyParser === "object" && bodyParser !== null) return {
+		enabled: true,
+		sizeLimit: parseSizeLimit(bodyParser.sizeLimit) ?? defaultSizeLimit
+	};
+	return {
+		enabled: true,
+		sizeLimit: defaultSizeLimit
+	};
+}
+//#endregion
+export { DEFAULT_PAGES_API_BODY_SIZE_LIMIT, parseSizeLimit, resolveBodyParserConfig };
+
+//# sourceMappingURL=pages-body-parser-config.js.map

package/dist/server/pages-body-parser-config.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"pages-body-parser-config.js","names":[],"sources":["../../src/server/pages-body-parser-config.ts"],"sourcesContent":["/**\n * Resolve the Pages Router `api.bodyParser` config from a route module export.\n *\n * Next.js API routes can opt out of automatic body parsing or raise the\n * default 1 MB size limit:\n *\n *   export const config = { api: { bodyParser: false } };\n *   export const config = { api: { bodyParser: { sizeLimit: '4mb' } } };\n *\n * `bodyParser: false` is critical for webhook handlers (Stripe, GitHub,\n * Slack, etc.) that must read the raw request bytes to verify an HMAC\n * signature. Silently parsing the body would consume the stream and break\n * signature verification — usually failing closed, sometimes failing open.\n *\n * @see https://nextjs.org/docs/pages/building-your-application/routing/api-routes#custom-config\n * @see Next.js: packages/next/src/server/api-utils/node/api-resolver.ts\n *\n * The format of `sizeLimit` mirrors what Next.js accepts via the `bytes`\n * package: a number of bytes, or a string with a unit suffix\n * (`\"500b\"`, `\"100kb\"`, `\"4mb\"`, `\"1gb\"`).\n */\n\n/**\n * Default Pages Router API body size limit, matching Next.js.\n */\nexport const DEFAULT_PAGES_API_BODY_SIZE_LIMIT = 1 * 1024 * 1024;\n\n/**\n * Resolved bodyParser configuration. When `enabled` is `false`, the body\n * MUST be passed through to the handler as a raw stream (or left unparsed\n * with `req.body === undefined`), so user code can read it itself.\n */\ntype ResolvedBodyParserConfig = { enabled: false } | { enabled: true; sizeLimit: number };\n\nconst SIZE_UNITS: Record<string, number> = {\n  b: 1,\n  kb: 1024,\n  mb: 1024 * 1024,\n  gb: 1024 * 1024 * 1024,\n  tb: 1024 * 1024 * 1024 * 1024,\n};\n\n/**\n * Parse a Next.js-style `sizeLimit` string (e.g. `\"4mb\"`, `\"100kb\"`, `\"1gb\"`)\n * or numeric byte value into a number of bytes. Returns `undefined` for\n * inputs that can't be parsed — callers should fall back to the default.\n *\n * Matches the format accepted by Next.js (the `bytes` package); we\n * implement it inline to avoid pulling a dependency for a tiny parser.\n */\nexport function parseSizeLimit(value: string | number | undefined): number | undefined {\n  if (value === undefined || value === null) return undefined;\n  if (typeof value === \"number\") {\n    return Number.isFinite(value) && value >= 0 ? value : undefined;\n  }\n  if (typeof value !== \"string\") return undefined;\n\n  const trimmed = value.trim().toLowerCase();\n  if (!trimmed) return undefined;\n\n  // Match `<number><unit?>` where number can be int/decimal and unit is one\n  // of b/kb/mb/gb/tb. The unit is optional — a bare number is bytes.\n  const match = /^(\\d+(?:\\.\\d+)?)\\s*(b|kb|mb|gb|tb)?$/.exec(trimmed);\n  if (!match) return undefined;\n\n  const amount = Number.parseFloat(match[1]);\n  if (!Number.isFinite(amount) || amount < 0) return undefined;\n\n  const unit = match[2] ?? \"b\";\n  const multiplier = SIZE_UNITS[unit];\n  if (multiplier === undefined) return undefined;\n\n  return Math.floor(amount * multiplier);\n}\n\n/**\n * Read the resolved `bodyParser` config from a route module's `config`\n * export. Defaults to enabled with the 1 MB Next.js default.\n */\nexport function resolveBodyParserConfig(\n  moduleConfig: { api?: { bodyParser?: boolean | { sizeLimit?: string | number } } } | undefined,\n  defaultSizeLimit: number = DEFAULT_PAGES_API_BODY_SIZE_LIMIT,\n): ResolvedBodyParserConfig {\n  const bodyParser = moduleConfig?.api?.bodyParser;\n\n  // Explicit opt-out: leave the body untouched so handlers can read raw bytes.\n  if (bodyParser === false) {\n    return { enabled: false };\n  }\n\n  // `true` or `undefined` → default behaviour.\n  if (bodyParser === undefined || bodyParser === true) {\n    return { enabled: true, sizeLimit: defaultSizeLimit };\n  }\n\n  // Object form: honour `sizeLimit` if present and parseable, else default.\n  if (typeof bodyParser === \"object\" && bodyParser !== null) {\n    const parsed = parseSizeLimit(bodyParser.sizeLimit);\n    return { enabled: true, sizeLimit: parsed ?? defaultSizeLimit };\n  }\n\n  // Anything else (truthy non-object/non-true) — be conservative and use\n  // the default, matching Next.js's `!== false` check.\n  return { enabled: true, sizeLimit: defaultSizeLimit };\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;AAyBA,MAAa,oCAAoC,IAAI,OAAO;AAS5D,MAAM,aAAqC;CACzC,GAAG;CACH,IAAI;CACJ,IAAI,OAAO;CACX,IAAI,OAAO,OAAO;CAClB,IAAI,OAAO,OAAO,OAAO;CAC1B;;;;;;;;;AAUD,SAAgB,eAAe,OAAwD;CACrF,IAAI,UAAU,KAAA,KAAa,UAAU,MAAM,OAAO,KAAA;CAClD,IAAI,OAAO,UAAU,UACnB,OAAO,OAAO,SAAS,MAAM,IAAI,SAAS,IAAI,QAAQ,KAAA;CAExD,IAAI,OAAO,UAAU,UAAU,OAAO,KAAA;CAEtC,MAAM,UAAU,MAAM,MAAM,CAAC,aAAa;CAC1C,IAAI,CAAC,SAAS,OAAO,KAAA;CAIrB,MAAM,QAAQ,uCAAuC,KAAK,QAAQ;CAClE,IAAI,CAAC,OAAO,OAAO,KAAA;CAEnB,MAAM,SAAS,OAAO,WAAW,MAAM,GAAG;CAC1C,IAAI,CAAC,OAAO,SAAS,OAAO,IAAI,SAAS,GAAG,OAAO,KAAA;CAGnD,MAAM,aAAa,WADN,MAAM,MAAM;CAEzB,IAAI,eAAe,KAAA,GAAW,OAAO,KAAA;CAErC,OAAO,KAAK,MAAM,SAAS,WAAW;;;;;;AAOxC,SAAgB,wBACd,cACA,mBAA2B,mCACD;CAC1B,MAAM,aAAa,cAAc,KAAK;CAGtC,IAAI,eAAe,OACjB,OAAO,EAAE,SAAS,OAAO;CAI3B,IAAI,eAAe,KAAA,KAAa,eAAe,MAC7C,OAAO;EAAE,SAAS;EAAM,WAAW;EAAkB;CAIvD,IAAI,OAAO,eAAe,YAAY,eAAe,MAEnD,OAAO;EAAE,SAAS;EAAM,WADT,eAAe,WAAW,UACA,IAAI;EAAkB;CAKjE,OAAO;EAAE,SAAS;EAAM,WAAW;EAAkB"}

package/dist/server/pages-data-route.d.ts

@@ -0,0 +1,77 @@
+//#region src/server/pages-data-route.d.ts
+/**
+ * Helpers for the Pages Router `/_next/data/{buildId}/{...page}.json` endpoint.
+ *
+ * Next.js uses this endpoint for client-side navigations in the Pages Router:
+ * `next/link` and `router.push()` fetch `pageProps` from this URL instead of
+ * doing a full HTML navigation. The server must:
+ *   1. Match the URL pattern and extract the page pathname (with the buildId
+ *      and `.json` extension removed, locale prefix preserved).
+ *   2. Normalize the URL BEFORE middleware runs so middleware sees the page
+ *      path (e.g. `/about`) rather than the raw `/_next/data/.../about.json`.
+ *   3. Invoke the same `getServerSideProps` / `getStaticProps` machinery as
+ *      the HTML page and serialize the resulting props as a JSON envelope:
+ *      `{ pageProps: ... }` with `Content-Type: application/json`.
+ *
+ * Ported from Next.js:
+ *   - `packages/next/src/server/normalizers/request/next-data.ts` — prefix/suffix matcher.
+ *   - `packages/next/src/server/base-server.ts` (`handleNextDataRequest`) — pipeline normalization.
+ *   - `packages/next/src/server/render.tsx` — JSON envelope emission (`isNextDataRequest`).
+ */
+type NextDataMatch = {
+  /**
+   * The normalized page pathname (with leading slash, no trailing slash,
+   * `.json` stripped, buildId stripped). For locale-prefixed requests like
+   * `/_next/data/<buildId>/en/about.json` this is `/en/about` — locale
+   * handling is done downstream by the existing `resolvePagesI18nRequest`
+   * pipeline so this helper does not need to know about i18n config.
+   */
+  pagePathname: string;
+};
+/**
+ * Returns true if the pathname looks like a `_next/data` request, regardless
+ * of buildId. Used by the request pipeline to short-circuit before middleware
+ * even when the buildId is wrong (so we can still return a 404 JSON response).
+ */
+declare function isNextDataPathname(pathname: string): boolean;
+/**
+ * Parse `/_next/data/<buildId>/<...page>.json` and return the normalized page
+ * pathname. Returns `null` if the pathname does not match the pattern or if
+ * the buildId segment does not match the server's buildId.
+ *
+ * The returned `pagePathname` is the page route path Next.js would render for
+ * the equivalent HTML navigation — including any locale prefix, which is then
+ * stripped by `resolvePagesI18nRequest` downstream.
+ *
+ * `/_next/data/<buildId>/about.json`         → `/about`
+ * `/_next/data/<buildId>/en/about.json`      → `/en/about`
+ * `/_next/data/<buildId>/index.json`         → `/`
+ * `/_next/data/<buildId>/en.json`            → `/en`
+ * `/_next/data/<wrong-id>/about.json`        → null
+ * `/_next/data/<buildId>/about`              → null  (missing .json suffix)
+ */
+declare function parseNextDataPathname(pathname: string, buildId: string): NextDataMatch | null;
+/**
+ * Build the JSON envelope returned by `/_next/data/<buildId>/<page>.json`.
+ * Mirrors Next.js' `RenderResult(JSON.stringify(props))` path in
+ * `packages/next/src/server/render.tsx` (search for `isNextDataRequest`).
+ *
+ * The envelope is the outer `props` object the React tree would receive:
+ *   { pageProps: {...}, /* optional locale data, redirect markers, etc. *\/ }
+ */
+declare function buildNextDataJsonResponse(pageProps: Record<string, unknown>, safeJsonStringify: (value: unknown) => string, init?: ResponseInit): Response;
+/**
+ * Build the 404 response Next.js returns for an unknown `_next/data` page.
+ * Next.js renders this as a normal 404 page, but the body shape that clients
+ * see for a missing page-data endpoint is the literal string `"{ }"` for the
+ * body and a 404 status with `application/json` so client-side hard-navigation
+ * fallback fires (see `__N_SSP` handling in `router.ts`).
+ *
+ * We match Next.js' behavior: 404 status + JSON content type. The body is an
+ * empty JSON object so clients that blindly call `res.json()` do not throw
+ * before checking the status code.
+ */
+declare function buildNextDataNotFoundResponse(): Response;
+//#endregion
+export { buildNextDataJsonResponse, buildNextDataNotFoundResponse, isNextDataPathname, parseNextDataPathname };
+//# sourceMappingURL=pages-data-route.d.ts.map

package/dist/server/pages-data-route.js

@@ -0,0 +1,98 @@
+//#region src/server/pages-data-route.ts
+/**
+* Helpers for the Pages Router `/_next/data/{buildId}/{...page}.json` endpoint.
+*
+* Next.js uses this endpoint for client-side navigations in the Pages Router:
+* `next/link` and `router.push()` fetch `pageProps` from this URL instead of
+* doing a full HTML navigation. The server must:
+*   1. Match the URL pattern and extract the page pathname (with the buildId
+*      and `.json` extension removed, locale prefix preserved).
+*   2. Normalize the URL BEFORE middleware runs so middleware sees the page
+*      path (e.g. `/about`) rather than the raw `/_next/data/.../about.json`.
+*   3. Invoke the same `getServerSideProps` / `getStaticProps` machinery as
+*      the HTML page and serialize the resulting props as a JSON envelope:
+*      `{ pageProps: ... }` with `Content-Type: application/json`.
+*
+* Ported from Next.js:
+*   - `packages/next/src/server/normalizers/request/next-data.ts` — prefix/suffix matcher.
+*   - `packages/next/src/server/base-server.ts` (`handleNextDataRequest`) — pipeline normalization.
+*   - `packages/next/src/server/render.tsx` — JSON envelope emission (`isNextDataRequest`).
+*/
+const NEXT_DATA_PREFIX = "/_next/data/";
+const NEXT_DATA_SUFFIX = ".json";
+/**
+* Returns true if the pathname looks like a `_next/data` request, regardless
+* of buildId. Used by the request pipeline to short-circuit before middleware
+* even when the buildId is wrong (so we can still return a 404 JSON response).
+*/
+function isNextDataPathname(pathname) {
+	return pathname.startsWith(NEXT_DATA_PREFIX) && pathname.endsWith(NEXT_DATA_SUFFIX);
+}
+/**
+* Parse `/_next/data/<buildId>/<...page>.json` and return the normalized page
+* pathname. Returns `null` if the pathname does not match the pattern or if
+* the buildId segment does not match the server's buildId.
+*
+* The returned `pagePathname` is the page route path Next.js would render for
+* the equivalent HTML navigation — including any locale prefix, which is then
+* stripped by `resolvePagesI18nRequest` downstream.
+*
+* `/_next/data/<buildId>/about.json`         → `/about`
+* `/_next/data/<buildId>/en/about.json`      → `/en/about`
+* `/_next/data/<buildId>/index.json`         → `/`
+* `/_next/data/<buildId>/en.json`            → `/en`
+* `/_next/data/<wrong-id>/about.json`        → null
+* `/_next/data/<buildId>/about`              → null  (missing .json suffix)
+*/
+function parseNextDataPathname(pathname, buildId) {
+	if (!buildId) return null;
+	if (!isNextDataPathname(pathname)) return null;
+	const expectedPrefix = `${NEXT_DATA_PREFIX}${buildId}/`;
+	if (!pathname.startsWith(expectedPrefix)) return null;
+	const rest = pathname.slice(expectedPrefix.length, -5);
+	if (rest.length === 0) return null;
+	if (rest === "index") return { pagePathname: "/" };
+	if (rest.endsWith("/index")) return { pagePathname: `/${rest.slice(0, -6)}` };
+	if (rest.startsWith("index/")) return { pagePathname: `/${rest.slice(6)}` };
+	return { pagePathname: `/${rest}` };
+}
+/**
+* Build the JSON envelope returned by `/_next/data/<buildId>/<page>.json`.
+* Mirrors Next.js' `RenderResult(JSON.stringify(props))` path in
+* `packages/next/src/server/render.tsx` (search for `isNextDataRequest`).
+*
+* The envelope is the outer `props` object the React tree would receive:
+*   { pageProps: {...}, /* optional locale data, redirect markers, etc. *\/ }
+*/
+function buildNextDataJsonResponse(pageProps, safeJsonStringify, init) {
+	const body = safeJsonStringify({ pageProps });
+	return new Response(body, {
+		status: init?.status ?? 200,
+		statusText: init?.statusText,
+		headers: {
+			"Content-Type": "application/json",
+			...init?.headers
+		}
+	});
+}
+/**
+* Build the 404 response Next.js returns for an unknown `_next/data` page.
+* Next.js renders this as a normal 404 page, but the body shape that clients
+* see for a missing page-data endpoint is the literal string `"{ }"` for the
+* body and a 404 status with `application/json` so client-side hard-navigation
+* fallback fires (see `__N_SSP` handling in `router.ts`).
+*
+* We match Next.js' behavior: 404 status + JSON content type. The body is an
+* empty JSON object so clients that blindly call `res.json()` do not throw
+* before checking the status code.
+*/
+function buildNextDataNotFoundResponse() {
+	return new Response("{}", {
+		status: 404,
+		headers: { "Content-Type": "application/json" }
+	});
+}
+//#endregion
+export { buildNextDataJsonResponse, buildNextDataNotFoundResponse, isNextDataPathname, parseNextDataPathname };
+
+//# sourceMappingURL=pages-data-route.js.map

package/dist/server/pages-data-route.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"pages-data-route.js","names":[],"sources":["../../src/server/pages-data-route.ts"],"sourcesContent":["/**\n * Helpers for the Pages Router `/_next/data/{buildId}/{...page}.json` endpoint.\n *\n * Next.js uses this endpoint for client-side navigations in the Pages Router:\n * `next/link` and `router.push()` fetch `pageProps` from this URL instead of\n * doing a full HTML navigation. The server must:\n *   1. Match the URL pattern and extract the page pathname (with the buildId\n *      and `.json` extension removed, locale prefix preserved).\n *   2. Normalize the URL BEFORE middleware runs so middleware sees the page\n *      path (e.g. `/about`) rather than the raw `/_next/data/.../about.json`.\n *   3. Invoke the same `getServerSideProps` / `getStaticProps` machinery as\n *      the HTML page and serialize the resulting props as a JSON envelope:\n *      `{ pageProps: ... }` with `Content-Type: application/json`.\n *\n * Ported from Next.js:\n *   - `packages/next/src/server/normalizers/request/next-data.ts` — prefix/suffix matcher.\n *   - `packages/next/src/server/base-server.ts` (`handleNextDataRequest`) — pipeline normalization.\n *   - `packages/next/src/server/render.tsx` — JSON envelope emission (`isNextDataRequest`).\n */\n\nconst NEXT_DATA_PREFIX = \"/_next/data/\";\nconst NEXT_DATA_SUFFIX = \".json\";\n\ntype NextDataMatch = {\n  /**\n   * The normalized page pathname (with leading slash, no trailing slash,\n   * `.json` stripped, buildId stripped). For locale-prefixed requests like\n   * `/_next/data/<buildId>/en/about.json` this is `/en/about` — locale\n   * handling is done downstream by the existing `resolvePagesI18nRequest`\n   * pipeline so this helper does not need to know about i18n config.\n   */\n  pagePathname: string;\n};\n\n/**\n * Returns true if the pathname looks like a `_next/data` request, regardless\n * of buildId. Used by the request pipeline to short-circuit before middleware\n * even when the buildId is wrong (so we can still return a 404 JSON response).\n */\nexport function isNextDataPathname(pathname: string): boolean {\n  return pathname.startsWith(NEXT_DATA_PREFIX) && pathname.endsWith(NEXT_DATA_SUFFIX);\n}\n\n/**\n * Parse `/_next/data/<buildId>/<...page>.json` and return the normalized page\n * pathname. Returns `null` if the pathname does not match the pattern or if\n * the buildId segment does not match the server's buildId.\n *\n * The returned `pagePathname` is the page route path Next.js would render for\n * the equivalent HTML navigation — including any locale prefix, which is then\n * stripped by `resolvePagesI18nRequest` downstream.\n *\n * `/_next/data/<buildId>/about.json`         → `/about`\n * `/_next/data/<buildId>/en/about.json`      → `/en/about`\n * `/_next/data/<buildId>/index.json`         → `/`\n * `/_next/data/<buildId>/en.json`            → `/en`\n * `/_next/data/<wrong-id>/about.json`        → null\n * `/_next/data/<buildId>/about`              → null  (missing .json suffix)\n */\nexport function parseNextDataPathname(pathname: string, buildId: string): NextDataMatch | null {\n  if (!buildId) return null;\n  if (!isNextDataPathname(pathname)) return null;\n\n  const expectedPrefix = `${NEXT_DATA_PREFIX}${buildId}/`;\n  // `/_next/data/<buildId>.json` (no trailing slash) is not a valid data req.\n  if (!pathname.startsWith(expectedPrefix)) return null;\n\n  const rest = pathname.slice(expectedPrefix.length, -NEXT_DATA_SUFFIX.length);\n\n  // Empty rest (`/_next/data/<buildId>/.json`) is not a valid page path.\n  if (rest.length === 0) return null;\n\n  // Next.js denormalizes `index` to `/` to mirror file-system page paths\n  // (`pages/index.tsx` → `/`). See `denormalizePagePath` in Next.js.\n  if (rest === \"index\") return { pagePathname: \"/\" };\n  if (rest.endsWith(\"/index\")) return { pagePathname: `/${rest.slice(0, -\"/index\".length)}` };\n\n  // The encoder (`getAssetPathFromRoute` in Next.js / `buildPagesDataPath` in\n  // vinext) prefixes any path beginning with `index` with an extra `index/`\n  // segment so an explicit `pages/index/foo.tsx` page (route `/index/foo`)\n  // round-trips through the data URL without colliding with `/foo`. Strip\n  // that prefix here.\n  if (rest.startsWith(\"index/\")) return { pagePathname: `/${rest.slice(\"index/\".length)}` };\n\n  return { pagePathname: `/${rest}` };\n}\n\n/**\n * Build the JSON envelope returned by `/_next/data/<buildId>/<page>.json`.\n * Mirrors Next.js' `RenderResult(JSON.stringify(props))` path in\n * `packages/next/src/server/render.tsx` (search for `isNextDataRequest`).\n *\n * The envelope is the outer `props` object the React tree would receive:\n *   { pageProps: {...}, /* optional locale data, redirect markers, etc. *\\/ }\n */\nexport function buildNextDataJsonResponse(\n  pageProps: Record<string, unknown>,\n  safeJsonStringify: (value: unknown) => string,\n  init?: ResponseInit,\n): Response {\n  const body = safeJsonStringify({ pageProps });\n  return new Response(body, {\n    status: init?.status ?? 200,\n    statusText: init?.statusText,\n    headers: {\n      \"Content-Type\": \"application/json\",\n      ...(init?.headers as Record<string, string> | undefined),\n    },\n  });\n}\n\n/**\n * Build the 404 response Next.js returns for an unknown `_next/data` page.\n * Next.js renders this as a normal 404 page, but the body shape that clients\n * see for a missing page-data endpoint is the literal string `\"{ }\"` for the\n * body and a 404 status with `application/json` so client-side hard-navigation\n * fallback fires (see `__N_SSP` handling in `router.ts`).\n *\n * We match Next.js' behavior: 404 status + JSON content type. The body is an\n * empty JSON object so clients that blindly call `res.json()` do not throw\n * before checking the status code.\n */\nexport function buildNextDataNotFoundResponse(): Response {\n  return new Response(\"{}\", {\n    status: 404,\n    headers: { \"Content-Type\": \"application/json\" },\n  });\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;AAoBA,MAAM,mBAAmB;AACzB,MAAM,mBAAmB;;;;;;AAkBzB,SAAgB,mBAAmB,UAA2B;CAC5D,OAAO,SAAS,WAAW,iBAAiB,IAAI,SAAS,SAAS,iBAAiB;;;;;;;;;;;;;;;;;;AAmBrF,SAAgB,sBAAsB,UAAkB,SAAuC;CAC7F,IAAI,CAAC,SAAS,OAAO;CACrB,IAAI,CAAC,mBAAmB,SAAS,EAAE,OAAO;CAE1C,MAAM,iBAAiB,GAAG,mBAAmB,QAAQ;CAErD,IAAI,CAAC,SAAS,WAAW,eAAe,EAAE,OAAO;CAEjD,MAAM,OAAO,SAAS,MAAM,eAAe,QAAQ,GAAyB;CAG5E,IAAI,KAAK,WAAW,GAAG,OAAO;CAI9B,IAAI,SAAS,SAAS,OAAO,EAAE,cAAc,KAAK;CAClD,IAAI,KAAK,SAAS,SAAS,EAAE,OAAO,EAAE,cAAc,IAAI,KAAK,MAAM,GAAG,GAAiB,IAAI;CAO3F,IAAI,KAAK,WAAW,SAAS,EAAE,OAAO,EAAE,cAAc,IAAI,KAAK,MAAM,EAAgB,IAAI;CAEzF,OAAO,EAAE,cAAc,IAAI,QAAQ;;;;;;;;;;AAWrC,SAAgB,0BACd,WACA,mBACA,MACU;CACV,MAAM,OAAO,kBAAkB,EAAE,WAAW,CAAC;CAC7C,OAAO,IAAI,SAAS,MAAM;EACxB,QAAQ,MAAM,UAAU;EACxB,YAAY,MAAM;EAClB,SAAS;GACP,gBAAgB;GAChB,GAAI,MAAM;GACX;EACF,CAAC;;;;;;;;;;;;;AAcJ,SAAgB,gCAA0C;CACxD,OAAO,IAAI,SAAS,MAAM;EACxB,QAAQ;EACR,SAAS,EAAE,gBAAgB,oBAAoB;EAChD,CAAC"}

package/dist/server/pages-default-404.d.ts

@@ -0,0 +1,31 @@
+//#region src/server/pages-default-404.d.ts
+/**
+ * Default 404 HTML body for the Pages Router.
+ *
+ * Used when a Pages Router request does not match any route (and the app has
+ * not supplied a custom `pages/404.tsx`). Mirrors the markup Next.js's
+ * `pages/_error.tsx` produces for a 404 response: a centered status / message
+ * pair plus minified theme CSS and dark-mode media query. The message string
+ * `"This page could not be found."` (note the trailing period) is the
+ * canonical body asserted by Next.js's deploy suite
+ * (`test/e2e/getserversideprops/test/index.test.ts`,
+ * `test/e2e/basepath/error-pages.test.ts`).
+ *
+ * Kept as a hand-rendered HTML literal rather than a React-rendered template
+ * because the Pages Router server entry is invoked from both Workers and the
+ * dev server before any React-renderer wiring is available for this path —
+ * matching the lightweight build-time strategy Next.js uses for its packaged
+ * `_error` static fallback. See:
+ *   .nextjs-ref/packages/next/src/pages/_error.tsx
+ */
+/**
+ * Build the Next.js-compatible default 404 HTML response for the Pages Router.
+ * Content-type is `text/html; charset=utf-8`, matching Next.js's
+ * `pages-handler` 404 response.
+ */
+declare function buildDefaultPagesNotFoundResponse(): Response;
+/** Exported for tests / callers that need the raw HTML body. */
+declare const DEFAULT_PAGES_NOT_FOUND_HTML = "<!DOCTYPE html><html><head><meta charset=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width\"/><title>404: This page could not be found.</title><meta name=\"next-head-count\" content=\"2\"/><style data-next-hide-fouc=\"true\">body{display:none}</style><noscript data-next-hide-fouc=\"true\"><style>body{display:block}</style></noscript></head><body><div id=\"__next\"><div style=\"font-family:system-ui,&quot;Segoe UI&quot;,Roboto,Helvetica,Arial,sans-serif,&quot;Apple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;;height:100vh;text-align:center;display:flex;flex-direction:column;align-items:center;justify-content:center\"><div style=\"line-height:48px\"><style>body{color:#000;background:#fff;margin:0}.next-error-h1{border-right:1px solid rgba(0,0,0,.3)}@media (prefers-color-scheme:dark){body{color:#fff;background:#000}.next-error-h1{border-right:1px solid rgba(255,255,255,.3)}}</style><h1 class=\"next-error-h1\" style=\"display:inline-block;margin:0 20px 0 0;padding-right:23px;font-size:24px;font-weight:500;vertical-align:top\">404</h1><div style=\"display:inline-block\"><h2 style=\"font-size:14px;font-weight:400;line-height:28px\">This page could not be found.</h2></div></div></div></div></body></html>";
+//#endregion
+export { DEFAULT_PAGES_NOT_FOUND_HTML, buildDefaultPagesNotFoundResponse };
+//# sourceMappingURL=pages-default-404.d.ts.map

package/dist/server/pages-default-404.js

@@ -0,0 +1,40 @@
+//#region src/server/pages-default-404.ts
+/**
+* Default 404 HTML body for the Pages Router.
+*
+* Used when a Pages Router request does not match any route (and the app has
+* not supplied a custom `pages/404.tsx`). Mirrors the markup Next.js's
+* `pages/_error.tsx` produces for a 404 response: a centered status / message
+* pair plus minified theme CSS and dark-mode media query. The message string
+* `"This page could not be found."` (note the trailing period) is the
+* canonical body asserted by Next.js's deploy suite
+* (`test/e2e/getserversideprops/test/index.test.ts`,
+* `test/e2e/basepath/error-pages.test.ts`).
+*
+* Kept as a hand-rendered HTML literal rather than a React-rendered template
+* because the Pages Router server entry is invoked from both Workers and the
+* dev server before any React-renderer wiring is available for this path —
+* matching the lightweight build-time strategy Next.js uses for its packaged
+* `_error` static fallback. See:
+*   .nextjs-ref/packages/next/src/pages/_error.tsx
+*/
+const STATUS = 404;
+const MESSAGE = "This page could not be found.";
+const HTML = `<!DOCTYPE html><html><head><meta charset="utf-8"/><meta name="viewport" content="width=device-width"/><title>${STATUS}: ${MESSAGE}</title><meta name="next-head-count" content="2"/><style data-next-hide-fouc="true">body{display:none}</style><noscript data-next-hide-fouc="true"><style>body{display:block}</style></noscript></head><body><div id="__next"><div style="font-family:system-ui,&quot;Segoe UI&quot;,Roboto,Helvetica,Arial,sans-serif,&quot;Apple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;;height:100vh;text-align:center;display:flex;flex-direction:column;align-items:center;justify-content:center"><div style="line-height:48px"><style>body{color:#000;background:#fff;margin:0}.next-error-h1{border-right:1px solid rgba(0,0,0,.3)}@media (prefers-color-scheme:dark){body{color:#fff;background:#000}.next-error-h1{border-right:1px solid rgba(255,255,255,.3)}}</style><h1 class="next-error-h1" style="display:inline-block;margin:0 20px 0 0;padding-right:23px;font-size:24px;font-weight:500;vertical-align:top">${STATUS}</h1><div style="display:inline-block"><h2 style="font-size:14px;font-weight:400;line-height:28px">${MESSAGE}</h2></div></div></div></div></body></html>`;
+/**
+* Build the Next.js-compatible default 404 HTML response for the Pages Router.
+* Content-type is `text/html; charset=utf-8`, matching Next.js's
+* `pages-handler` 404 response.
+*/
+function buildDefaultPagesNotFoundResponse() {
+	return new Response(HTML, {
+		status: STATUS,
+		headers: { "Content-Type": "text/html; charset=utf-8" }
+	});
+}
+/** Exported for tests / callers that need the raw HTML body. */
+const DEFAULT_PAGES_NOT_FOUND_HTML = HTML;
+//#endregion
+export { DEFAULT_PAGES_NOT_FOUND_HTML, buildDefaultPagesNotFoundResponse };
+
+//# sourceMappingURL=pages-default-404.js.map

package/dist/server/pages-default-404.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"pages-default-404.js","names":[],"sources":["../../src/server/pages-default-404.ts"],"sourcesContent":["/**\n * Default 404 HTML body for the Pages Router.\n *\n * Used when a Pages Router request does not match any route (and the app has\n * not supplied a custom `pages/404.tsx`). Mirrors the markup Next.js's\n * `pages/_error.tsx` produces for a 404 response: a centered status / message\n * pair plus minified theme CSS and dark-mode media query. The message string\n * `\"This page could not be found.\"` (note the trailing period) is the\n * canonical body asserted by Next.js's deploy suite\n * (`test/e2e/getserversideprops/test/index.test.ts`,\n * `test/e2e/basepath/error-pages.test.ts`).\n *\n * Kept as a hand-rendered HTML literal rather than a React-rendered template\n * because the Pages Router server entry is invoked from both Workers and the\n * dev server before any React-renderer wiring is available for this path —\n * matching the lightweight build-time strategy Next.js uses for its packaged\n * `_error` static fallback. See:\n *   .nextjs-ref/packages/next/src/pages/_error.tsx\n */\n\nconst STATUS = 404;\nconst MESSAGE = \"This page could not be found.\";\n\nconst CSS = `body{color:#000;background:#fff;margin:0}.next-error-h1{border-right:1px solid rgba(0,0,0,.3)}@media (prefers-color-scheme:dark){body{color:#fff;background:#000}.next-error-h1{border-right:1px solid rgba(255,255,255,.3)}}`;\n\nconst HTML = `<!DOCTYPE html><html><head><meta charset=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width\"/><title>${STATUS}: ${MESSAGE}</title><meta name=\"next-head-count\" content=\"2\"/><style data-next-hide-fouc=\"true\">body{display:none}</style><noscript data-next-hide-fouc=\"true\"><style>body{display:block}</style></noscript></head><body><div id=\"__next\"><div style=\"font-family:system-ui,&quot;Segoe UI&quot;,Roboto,Helvetica,Arial,sans-serif,&quot;Apple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;;height:100vh;text-align:center;display:flex;flex-direction:column;align-items:center;justify-content:center\"><div style=\"line-height:48px\"><style>${CSS}</style><h1 class=\"next-error-h1\" style=\"display:inline-block;margin:0 20px 0 0;padding-right:23px;font-size:24px;font-weight:500;vertical-align:top\">${STATUS}</h1><div style=\"display:inline-block\"><h2 style=\"font-size:14px;font-weight:400;line-height:28px\">${MESSAGE}</h2></div></div></div></div></body></html>`;\n\n/**\n * Build the Next.js-compatible default 404 HTML response for the Pages Router.\n * Content-type is `text/html; charset=utf-8`, matching Next.js's\n * `pages-handler` 404 response.\n */\nexport function buildDefaultPagesNotFoundResponse(): Response {\n  return new Response(HTML, {\n    status: STATUS,\n    headers: { \"Content-Type\": \"text/html; charset=utf-8\" },\n  });\n}\n\n/** Exported for tests / callers that need the raw HTML body. */\nexport const DEFAULT_PAGES_NOT_FOUND_HTML = HTML;\n"],"mappings":";;;;;;;;;;;;;;;;;;;;AAoBA,MAAM,SAAS;AACf,MAAM,UAAU;AAIhB,MAAM,OAAO,gHAAgH,OAAO,IAAI,QAAQ,u3BAAgqB,OAAO,qGAAqG,QAAQ;;;;;;AAOp6B,SAAgB,oCAA8C;CAC5D,OAAO,IAAI,SAAS,MAAM;EACxB,QAAQ;EACR,SAAS,EAAE,gBAAgB,4BAA4B;EACxD,CAAC;;;AAIJ,MAAa,+BAA+B"}