@timber-js/app 0.2.0-alpha.158 → 0.2.0-alpha.159

package/src/server/client-module-map.ts

@@ -1,58 +0,0 @@
-/**
- * Client module map — maps client reference IDs to their SSR module loaders.
- *
- * When the RSC stream contains a client component reference (from a
- * "use client" module), the SSR environment needs to resolve it to the
- * actual component module so it can render the component to HTML.
- *
- * The @vitejs/plugin-rsc SSR runtime handles this internally via its
- * setRequireModule hook — it imports client reference modules from the
- * SSR environment's module graph. This module provides the configuration
- * bridge between timber's entry system and the RSC plugin's runtime.
- *
- * Design docs: 18-build-system.md §"Entry Files", 02-rendering-pipeline.md
- */
-
-/**
- * Client reference metadata used during SSR to resolve client components.
- *
- * The RSC plugin tracks these internally via `clientReferenceMetaMap`.
- * At SSR time, when `createFromReadableStream` encounters a client
- * reference in the RSC payload, it uses the module map to import the
- * actual component for server-side HTML rendering.
- */
-export interface ClientModuleEntry {
-  /** The module ID (Vite-resolved file path) */
-  id: string;
-  /** The export name (e.g., 'default', 'Counter') */
-  name: string;
-  /** Async module loader */
-  load: () => Promise<Record<string, unknown>>;
-}
-
-/**
- * Create a client module map for SSR resolution.
- *
- * In dev mode, the RSC plugin's SSR runtime (`@vitejs/plugin-rsc/ssr`)
- * handles client reference resolution automatically via its initialize()
- * function which sets up `setRequireModule` with dynamic imports through
- * Vite's dev server. No explicit module map is needed.
- *
- * In production builds, the RSC plugin generates a `virtual:vite-rsc/client-references`
- * module that maps client reference IDs to their chunk imports. The SSR
- * runtime reads this at startup.
- *
- * This function returns an empty map as a placeholder — the actual
- * resolution is handled by the RSC plugin's runtime internals.
- */
-export function createClientModuleMap(): Record<string, ClientModuleEntry> {
-  // The @vitejs/plugin-rsc SSR runtime handles client reference
-  // resolution internally. In dev mode, it uses Vite's module runner
-  // to dynamically import client modules. In production, it reads
-  // from the virtual:vite-rsc/client-references manifest.
-  //
-  // This empty map serves as the timber-side type contract. Framework
-  // code that needs to interact with client references at a higher
-  // level (e.g., collecting CSS deps, prefetch hints) can extend this.
-  return {};
-}

package/src/shared/head-header.ts

@@ -1,69 +0,0 @@
-/**
- * Shared encode/decode for the X-Timber-Head response header.
- *
- * Head elements (title, meta, link) are forwarded to the client as a JSON
- * payload in a response header on both the navigation path (RSC payload
- * responses) and the action-revalidation path. HTTP header values must be
- * ByteStrings — any character above U+00FF (em dash, curly quotes, emoji,
- * CJK) makes `new Response(...)` throw. Percent-encoding via
- * encodeURIComponent keeps the value ASCII-safe.
- *
- * This module is the single source of truth for the wire format. Both
- * server emit sites (rsc-entry/rsc-payload.ts, action-handler.ts) and both
- * client parse sites (rsc-fetch.ts, browser-entry/action-dispatch.ts) MUST
- * use it — changing one side alone breaks the other. See TIM-1058.
- *
- * Isomorphic: no server or client imports allowed here.
- *
- * See design/16-metadata.md and design/08-forms-and-actions.md.
- */
-
-/** Header name for resolved head elements. */
-export const HEAD_HEADER = 'X-Timber-Head';
-
-/**
- * Maximum encoded payload size in characters (ASCII after encoding, so
- * characters === bytes). Headers aren't meant for unbounded payloads;
- * oversized head metadata is skipped rather than truncated — the client
- * keeps its current head, which degrades gracefully.
- */
-export const HEAD_HEADER_MAX_LENGTH = 4096;
-
-/**
- * A rendered head element descriptor — the structural shape on the wire.
- * Matches the server's `HeadElement` (route-element-builder.ts); the client
- * narrows `tag` to 'title' | 'meta' | 'link' when applying to the DOM.
- */
-export interface HeadElementPayload {
-  tag: string;
-  content?: string;
-  attrs?: Record<string, string | null>;
-}
-
-/**
- * Encode head elements for the X-Timber-Head header.
- *
- * Returns the percent-encoded JSON string, or null when the encoded
- * payload exceeds HEAD_HEADER_MAX_LENGTH (caller skips the header).
- */
-export function encodeHeadHeader(headElements: HeadElementPayload[]): string | null {
-  const encoded = encodeURIComponent(JSON.stringify(headElements));
-  return encoded.length <= HEAD_HEADER_MAX_LENGTH ? encoded : null;
-}
-
-/**
- * Decode an X-Timber-Head header value back into head elements.
- *
- * Returns null when the value is missing or malformed (corrupted
- * percent-encoding or invalid JSON) — callers treat null as "no head
- * update" rather than failing the navigation or action.
- */
-export function decodeHeadHeader(header: string | null): HeadElementPayload[] | null {
-  if (!header) return null;
-  try {
-    const parsed = JSON.parse(decodeURIComponent(header));
-    return Array.isArray(parsed) ? parsed : null;
-  } catch {
-    return null;
-  }
-}