@warlock.js/web 5.0.2 → 5.2.0

package/esm/server/buffered-response.mjs

@@ -1,115 +0,0 @@
-//#region ../web/src/server/buffered-response.ts
-/**
-* Runtime brand behind `LoaderShortCircuit` (web/src/context.ts:13-17
-* declares the compile-time half). A loader RETURNS this from
-* `response.redirect()` / `response.notFound()`; the settle stage detects it
-* by the symbol, never by shape.
-*/
-const LOADER_SHORT_CIRCUIT = Symbol("warlock.loader.shortCircuit");
-function isLoaderShortCircuit(value) {
-	return typeof value === "object" && value !== null && value[LOADER_SHORT_CIRCUIT] === true;
-}
-function shortCircuitSignal(init) {
-	return {
-		...init,
-		[LOADER_SHORT_CIRCUIT]: true
-	};
-}
-function createBufferedResponse() {
-	const buffer = {
-		headers: [],
-		cookies: []
-	};
-	const response = {
-		header(key, value) {
-			buffer.headers.push({
-				key,
-				value
-			});
-			return response;
-		},
-		cookie(name, value, options) {
-			buffer.cookies.push({
-				name,
-				value,
-				options
-			});
-			return response;
-		},
-		setStatusCode(statusCode) {
-			buffer.statusCode = statusCode;
-			return response;
-		},
-		/**
-		* A redirect is a status AND a `Location`; both belong in the buffer.
-		*
-		* Writing only `buffer.statusCode` here and carrying the URL out on the
-		* branded return value split one answer across two channels, and the
-		* emit only ever drained the first: the document path applied
-		* `bundle.commit.headers` and never read `bundle.shortCircuit`, so the
-		* browser got a bare `302` with an empty body and stayed put
-		* (design/loader-endpoint-seam-2026-08-23.md §5).
-		*
-		* Putting `Location` in the buffer fixes it once, at the declaration,
-		* for every consumer: the commit stage's live mirror
-		* (`execute-page-request.ts` commitBuffers — which mirrors headers and
-		* status only; its cookie half was removed so `Set-Cookie` is not
-		* appended twice, and `Location` rides the header half),
-		* `bundle.commit.headers`, `finishRender`'s header map, and the handler's
-		* `response.headers()` all carry it without any of them learning what a
-		* redirect is. The
-		* alternative — special-casing `shortCircuit.kind` at the emit — would
-		* have to be re-implemented by every emit path that ever exists, which
-		* is precisely how this shipped unnoticed the first time.
-		*
-		* The signal is still returned and still branded: the buffer says what
-		* the response should LOOK like, the signal says the pipeline must STOP.
-		* Those are different facts and both are still needed.
-		*/
-		redirect(url, statusCode = 302) {
-			buffer.statusCode = statusCode;
-			buffer.headers.push({
-				key: "Location",
-				value: url
-			});
-			return shortCircuitSignal({
-				kind: "redirect",
-				statusCode,
-				url
-			});
-		},
-		/** Same shape as `redirect`, at 301 — deliberately not special-cased. */
-		permanentRedirect(url) {
-			buffer.statusCode = 301;
-			buffer.headers.push({
-				key: "Location",
-				value: url
-			});
-			return shortCircuitSignal({
-				kind: "redirect",
-				statusCode: 301,
-				url
-			});
-		},
-		/**
-		* The other short-circuit kind. It shares the signal shape but has no
-		* URL, so it writes no `Location` — a 404 that redirects is not a thing.
-		*/
-		notFound(body) {
-			buffer.statusCode = 404;
-			return shortCircuitSignal({
-				kind: "notFound",
-				statusCode: 404,
-				body
-			});
-		}
-	};
-	return {
-		response,
-		buffer
-	};
-}
-
-//#endregion
-export { LOADER_SHORT_CIRCUIT, createBufferedResponse, isLoaderShortCircuit };
-//# sourceMappingURL=buffered-response.mjs.map

package/esm/server/buffered-response.mjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"buffered-response.mjs","names":[],"sources":["../../../../../../../web/src/server/buffered-response.ts"],"sourcesContent":["import type { LoaderShortCircuit, WebResponse } from \"../context\";\n\n/**\n * The per-loader response facade for pipeline stage 6.\n *\n * Loaders run in PARALLEL and never see the real `Response`: core's\n * `Response.header`/`cookie` write straight through to the fastify reply\n * (core/src/http/response.ts:919-923, :955-967), so three concurrent loaders\n * writing directly would interleave nondeterministically and a discarded\n * layer's writes could never be taken back. Instead each loader gets one of\n * these facades; every write lands in a buffer, and the pipeline's\n * settle/commit stage applies the surviving buffers to\n * the real response root→leaf, per cookie name / header key.\n */\n\nexport type BufferedHeader = {\n  key: string;\n  value: string;\n};\n\nexport type BufferedCookie = {\n  name: string;\n  value: unknown;\n  options?: Record<string, unknown>;\n};\n\nexport type ResponseBuffer = {\n  headers: BufferedHeader[];\n  cookies: BufferedCookie[];\n  statusCode?: number;\n};\n\n/**\n * Runtime brand behind `LoaderShortCircuit` (web/src/context.ts:13-17\n * declares the compile-time half). A loader RETURNS this from\n * `response.redirect()` / `response.notFound()`; the settle stage detects it\n * by the symbol, never by shape.\n */\nexport const LOADER_SHORT_CIRCUIT = Symbol(\"warlock.loader.shortCircuit\");\n\nexport type LoaderShortCircuitSignal = LoaderShortCircuit & {\n  kind: \"redirect\" | \"notFound\";\n  statusCode: number;\n  url?: string;\n  body?: unknown;\n};\n\nexport function isLoaderShortCircuit(value: unknown): value is LoaderShortCircuitSignal {\n  return (\n    typeof value === \"object\" &&\n    value !== null &&\n    (value as Record<PropertyKey, unknown>)[LOADER_SHORT_CIRCUIT] === true\n  );\n}\n\nfunction shortCircuitSignal(\n  init: Omit<LoaderShortCircuitSignal, keyof LoaderShortCircuit>,\n): LoaderShortCircuitSignal {\n  return { ...init, [LOADER_SHORT_CIRCUIT]: true } as unknown as LoaderShortCircuitSignal;\n}\n\n/**\n * The loader-facing surface is `WebResponse` (web/src/context.ts:73-88) plus\n * `cookie()`, which the commit contract needs so buffers can be applied\n * per cookie name.\n */\nexport type BufferedWebResponse = WebResponse & {\n  cookie(name: string, value: unknown, options?: Record<string, unknown>): BufferedWebResponse;\n};\n\nexport function createBufferedResponse(): {\n  response: BufferedWebResponse;\n  buffer: ResponseBuffer;\n} {\n  const buffer: ResponseBuffer = { headers: [], cookies: [] };\n\n  const response: BufferedWebResponse = {\n    header(key: string, value: string) {\n      buffer.headers.push({ key, value });\n      return response;\n    },\n\n    cookie(name: string, value: unknown, options?: Record<string, unknown>) {\n      buffer.cookies.push({ name, value, options });\n      return response;\n    },\n\n    setStatusCode(statusCode: number) {\n      buffer.statusCode = statusCode;\n      return response;\n    },\n\n    /**\n     * A redirect is a status AND a `Location`; both belong in the buffer.\n     *\n     * Writing only `buffer.statusCode` here and carrying the URL out on the\n     * branded return value split one answer across two channels, and the\n     * emit only ever drained the first: the document path applied\n     * `bundle.commit.headers` and never read `bundle.shortCircuit`, so the\n     * browser got a bare `302` with an empty body and stayed put\n     * (design/loader-endpoint-seam-2026-08-23.md §5).\n     *\n     * Putting `Location` in the buffer fixes it once, at the declaration,\n     * for every consumer: the commit stage's live mirror\n     * (`execute-page-request.ts` commitBuffers — which mirrors headers and\n     * status only; its cookie half was removed so `Set-Cookie` is not\n     * appended twice, and `Location` rides the header half),\n     * `bundle.commit.headers`, `finishRender`'s header map, and the handler's\n     * `response.headers()` all carry it without any of them learning what a\n     * redirect is. The\n     * alternative — special-casing `shortCircuit.kind` at the emit — would\n     * have to be re-implemented by every emit path that ever exists, which\n     * is precisely how this shipped unnoticed the first time.\n     *\n     * The signal is still returned and still branded: the buffer says what\n     * the response should LOOK like, the signal says the pipeline must STOP.\n     * Those are different facts and both are still needed.\n     */\n    redirect(url: string, statusCode = 302) {\n      buffer.statusCode = statusCode;\n      buffer.headers.push({ key: \"Location\", value: url });\n      return shortCircuitSignal({ kind: \"redirect\", statusCode, url });\n    },\n\n    /** Same shape as `redirect`, at 301 — deliberately not special-cased. */\n    permanentRedirect(url: string) {\n      buffer.statusCode = 301;\n      buffer.headers.push({ key: \"Location\", value: url });\n      return shortCircuitSignal({ kind: \"redirect\", statusCode: 301, url });\n    },\n\n    /**\n     * The other short-circuit kind. It shares the signal shape but has no\n     * URL, so it writes no `Location` — a 404 that redirects is not a thing.\n     */\n    notFound(body?: unknown) {\n      buffer.statusCode = 404;\n      return shortCircuitSignal({ kind: \"notFound\", statusCode: 404, body });\n    },\n  };\n\n  return { response, buffer };\n}\n"],"mappings":";;;;;;;AAsCA,MAAa,uBAAuB,OAAO,6BAA6B;AASxE,SAAgB,qBAAqB,OAAmD;CACtF,OACE,OAAO,UAAU,YACjB,UAAU,QACT,MAAuC,0BAA0B;AAEtE;AAEA,SAAS,mBACP,MAC0B;CAC1B,OAAO;EAAE,GAAG;GAAO,uBAAuB;CAAK;AACjD;AAWA,SAAgB,yBAGd;CACA,MAAM,SAAyB;EAAE,SAAS,CAAC;EAAG,SAAS,CAAC;CAAE;CAE1D,MAAM,WAAgC;EACpC,OAAO,KAAa,OAAe;GACjC,OAAO,QAAQ,KAAK;IAAE;IAAK;GAAM,CAAC;GAClC,OAAO;EACT;EAEA,OAAO,MAAc,OAAgB,SAAmC;GACtE,OAAO,QAAQ,KAAK;IAAE;IAAM;IAAO;GAAQ,CAAC;GAC5C,OAAO;EACT;EAEA,cAAc,YAAoB;GAChC,OAAO,aAAa;GACpB,OAAO;EACT;;;;;;;;;;;;;;;;;;;;;;;;;;;EA4BA,SAAS,KAAa,aAAa,KAAK;GACtC,OAAO,aAAa;GACpB,OAAO,QAAQ,KAAK;IAAE,KAAK;IAAY,OAAO;GAAI,CAAC;GACnD,OAAO,mBAAmB;IAAE,MAAM;IAAY;IAAY;GAAI,CAAC;EACjE;;EAGA,kBAAkB,KAAa;GAC7B,OAAO,aAAa;GACpB,OAAO,QAAQ,KAAK;IAAE,KAAK;IAAY,OAAO;GAAI,CAAC;GACnD,OAAO,mBAAmB;IAAE,MAAM;IAAY,YAAY;IAAK;GAAI,CAAC;EACtE;;;;;EAMA,SAAS,MAAgB;GACvB,OAAO,aAAa;GACpB,OAAO,mBAAmB;IAAE,MAAM;IAAY,YAAY;IAAK;GAAK,CAAC;EACvE;CACF;CAEA,OAAO;EAAE;EAAU;CAAO;AAC5B"}