@timber-js/app 0.2.0-alpha.97 → 0.2.0-alpha.99

package/dist/server/page-deny-boundary.d.ts

@@ -1,31 +0,0 @@
-/**
- * PageDenyBoundary — catches DenySignal from page components server-side.
- *
- * Wraps a server component page by calling it as an async function (the same
- * thing React Flight does internally). If the page throws DenySignal, the
- * boundary catches it and renders the matching deny page as a normal element.
- * No error reaches React Flight — the Flight stream is clean, SSR succeeds,
- * and the entire request uses a single renderToReadableStream call.
- *
- * Client component pages ('use client') are NOT wrapped — they can't call
- * deny() (server-only API) and must go through createElement normally.
- *
- * See design/04-authorization.md, design/10-error-handling.md, TIM-666.
- */
-import type { DenyPageEntry } from './deny-page-resolver.js';
-/**
- * Async server component that wraps a page call with DenySignal catching.
- *
- * Calls the page component as an async function, awaits it, and catches
- * DenySignal. On catch, renders the deny page in-tree. On success, returns
- * the page's rendered output normally.
- */
-export declare function PageDenyBoundary({ Page, route, denyPages, }: {
-    /** The page server component function. */
-    Page: (...args: unknown[]) => unknown;
-    /** Route path for OTEL tracing. */
-    route: string;
-    /** Deny page fallback chain from the segment chain. */
-    denyPages: DenyPageEntry[];
-}): Promise<React.ReactElement>;
-//# sourceMappingURL=page-deny-boundary.d.ts.map

package/dist/server/page-deny-boundary.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"page-deny-boundary.d.ts","sourceRoot":"","sources":["../../src/server/page-deny-boundary.tsx"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AAGH,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,yBAAyB,CAAC;AAI7D;;;;;;GAMG;AACH,wBAAsB,gBAAgB,CAAC,EACrC,IAAI,EACJ,KAAK,EACL,SAAS,GACV,EAAE;IACD,0CAA0C;IAC1C,IAAI,EAAE,CAAC,GAAG,IAAI,EAAE,OAAO,EAAE,KAAK,OAAO,CAAC;IACtC,mCAAmC;IACnC,KAAK,EAAE,MAAM,CAAC;IACd,uDAAuD;IACvD,SAAS,EAAE,aAAa,EAAE,CAAC;CAC5B,GAAG,OAAO,CAAC,KAAK,CAAC,YAAY,CAAC,CAiB9B"}

package/src/server/dev-fetch-instrumentation.ts

@@ -1,96 +0,0 @@
-/**
- * Dev-mode fetch instrumentation — patches globalThis.fetch to create OTEL
- * spans for every fetch call, giving visibility into async data fetching
- * in the dev request log tree.
- *
- * Only activated in dev mode — zero overhead in production.
- *
- * The spans are automatically children of the active OTEL context (e.g. a
- * timber.page or timber.layout span), so they appear nested under the
- * component that initiated the fetch in the dev log tree.
- *
- * Design ref: 17-logging.md §"Dev Logging", LOCAL-289
- */
-
-import * as api from '@opentelemetry/api';
-
-export type DevFetchCleanup = () => void;
-
-/**
- * Patch globalThis.fetch to wrap every call in an OTEL span.
- *
- * Returns a cleanup function that restores the original fetch.
- * Only call this in dev mode.
- */
-export function instrumentDevFetch(): DevFetchCleanup {
-  const originalFetch = globalThis.fetch;
-  const tracer = api.trace.getTracer('timber.js');
-
-  globalThis.fetch = async (input: RequestInfo | URL, init?: RequestInit): Promise<Response> => {
-    const { method, url } = extractFetchInfo(input, init);
-
-    return tracer.startActiveSpan(
-      'timber.fetch',
-      {
-        attributes: {
-          'http.request.method': method,
-          'http.url': url,
-        },
-      },
-      async (span) => {
-        try {
-          const response = await originalFetch(input, init);
-
-          span.setAttribute('http.response.status_code', response.status);
-
-          // Surface cache status from standard headers
-          const cacheStatus =
-            response.headers.get('X-Cache') ?? response.headers.get('CF-Cache-Status');
-          if (cacheStatus) {
-            span.setAttribute('timber.cache_status', cacheStatus);
-          }
-
-          span.setStatus({ code: api.SpanStatusCode.OK });
-          span.end();
-          return response;
-        } catch (error) {
-          span.setStatus({ code: api.SpanStatusCode.ERROR });
-          if (error instanceof Error) {
-            span.setAttribute('timber.fetch_error', error.message);
-            span.recordException(error);
-          }
-          span.end();
-          throw error;
-        }
-      }
-    );
-  };
-
-  return () => {
-    globalThis.fetch = originalFetch;
-  };
-}
-
-/**
- * Extract method and URL from the various fetch() call signatures.
- */
-function extractFetchInfo(
-  input: RequestInfo | URL,
-  init?: RequestInit
-): { method: string; url: string } {
-  let method = init?.method ?? 'GET';
-  let url: string;
-
-  if (input instanceof Request) {
-    url = input.url;
-    if (!init?.method) {
-      method = input.method;
-    }
-  } else if (input instanceof URL) {
-    url = input.toString();
-  } else {
-    url = input;
-  }
-
-  return { method: method.toUpperCase(), url };
-}

package/src/server/dev-span-processor.ts

@@ -1,78 +0,0 @@
-/**
- * DevSpanProcessor — Custom OTEL SpanProcessor that drives dev log output.
- *
- * Collects completed spans per-request (correlated by trace ID). When the
- * root span (http.server.request) ends, all child spans are already collected
- * (child spans end before parent in OTEL). The processor formats the span
- * tree and writes it to stderr.
- *
- * This replaces the old DevLogEmitter/DevLogEvents system. OTEL spans are
- * now the single source of truth for dev logging — no more parallel event
- * systems that can drift.
- *
- * Design doc: 17-logging.md §"Dev Logging", 21-dev-server.md §"Dev Logging"
- */
-
-import type { SpanProcessor, ReadableSpan } from '@opentelemetry/sdk-trace-base';
-import type { Span, Context } from '@opentelemetry/api';
-import {
-  formatSpanTree,
-  formatSpanSummary,
-  formatJson,
-  type DevLogMode,
-  type DevLoggerConfig,
-} from './dev-logger.js';
-
-export class DevSpanProcessor implements SpanProcessor {
-  private spansByTrace = new Map<string, ReadableSpan[]>();
-  private mode: DevLogMode;
-  private config: DevLoggerConfig;
-
-  constructor(config: DevLoggerConfig) {
-    this.config = config;
-    this.mode = config.mode ?? 'tree';
-  }
-
-  onStart(_span: Span, _context: Context): void {
-    // No action needed on span start — we collect on end.
-  }
-
-  onEnd(span: ReadableSpan): void {
-    const traceId = span.spanContext().traceId;
-
-    let spans = this.spansByTrace.get(traceId);
-    if (!spans) {
-      spans = [];
-      this.spansByTrace.set(traceId, spans);
-    }
-    spans.push(span);
-
-    // Root span signals request completion — all child spans are already
-    // collected because OTEL ends child spans before parent spans.
-    if (span.name === 'http.server.request') {
-      const output = this.format(spans);
-      if (output) {
-        process.stderr.write(output);
-      }
-      this.spansByTrace.delete(traceId);
-    }
-  }
-
-  private format(spans: ReadableSpan[]): string {
-    if (this.mode === 'quiet') return '';
-    if (this.mode === 'json') return formatJson(spans);
-    if (this.mode === 'summary') return formatSpanSummary(spans, this.config);
-    // Both 'tree' and 'verbose' use the tree formatter.
-    // verbose will show additional detail (every component render) once
-    // component-level spans are wired.
-    return formatSpanTree(spans, this.config);
-  }
-
-  async shutdown(): Promise<void> {
-    this.spansByTrace.clear();
-  }
-
-  async forceFlush(): Promise<void> {
-    // Nothing to flush — output happens synchronously in onEnd.
-  }
-}

package/src/server/manifest-status-resolver.ts

@@ -1,215 +0,0 @@
-/**
- * Manifest-compatible status-code file resolver.
- *
- * The existing status-code-resolver.ts works with SegmentNode (Map-based).
- * This module works with ManifestSegmentNode (object-based) for use at
- * runtime in the RSC/SSR entries, where the route manifest provides
- * plain objects instead of Maps.
- *
- * Supports two format families:
- * - 'component' (default): .tsx/.jsx/.mdx status files → React rendering pipeline
- * - 'json': .json status files → raw JSON response, no React
- *
- * Follows the same fallback chains as status-code-resolver.ts:
- *
- * **Component chain (4xx):**
- *   Pass 1 — status files (leaf → root): {status}.tsx → 4xx.tsx
- *   Pass 2 — legacy compat (leaf → root): not-found.tsx / forbidden.tsx / unauthorized.tsx
- *   Pass 3 — error.tsx (leaf → root)
- *   Pass 4 — framework default (returns null)
- *
- * **JSON chain (4xx):**
- *   Pass 1 — json status files (leaf → root): {status}.json → 4xx.json
- *   Pass 2 — framework default JSON (returns null, caller provides bare JSON)
- *
- * See design/10-error-handling.md §"Status-Code Files"
- */
-
-import type { ManifestSegmentNode } from './route-matcher.js';
-
-// ─── Types ───────────────────────────────────────────────────────────────────
-
-/** A file reference in the manifest (lazy import + path). */
-interface ManifestFile {
-  load: () => Promise<unknown>;
-  filePath: string;
-}
-
-/** How the status-code file was matched. */
-export type ManifestStatusFileKind =
-  | 'exact' // e.g. 403.tsx matched status 403
-  | 'category' // e.g. 4xx.tsx matched status 403
-  | 'legacy' // e.g. not-found.tsx matched status 404
-  | 'error'; // error.tsx as last resort
-
-/** Response format family for status-code resolution. */
-export type ManifestStatusFileFormat = 'component' | 'json';
-
-/** Result of resolving a status-code file from manifest segments. */
-export interface ManifestStatusFileResolution {
-  /** The matched manifest file (has load() and filePath). */
-  file: ManifestFile;
-  /** The HTTP status code (always the original status, not the file's code). */
-  status: number;
-  /** How the file was matched. */
-  kind: ManifestStatusFileKind;
-  /** Index into the segments array where the file was found. */
-  segmentIndex: number;
-}
-
-// ─── Legacy Compat Mapping ───────────────────────────────────────────────────
-
-const LEGACY_FILE_TO_STATUS: Record<string, number> = {
-  'not-found': 404,
-  'forbidden': 403,
-  'unauthorized': 401,
-};
-
-// ─── Resolver ────────────────────────────────────────────────────────────────
-
-/**
- * Resolve the status-code file to render for a given HTTP status code,
- * using manifest segment nodes (plain objects, not Maps).
- *
- * @param status - The HTTP status code (4xx or 5xx).
- * @param segments - The matched segment chain from root (index 0) to leaf (last).
- * @param format - The response format family ('component' or 'json'). Defaults to 'component'.
- */
-export function resolveManifestStatusFile(
-  status: number,
-  segments: ReadonlyArray<ManifestSegmentNode>,
-  format: ManifestStatusFileFormat = 'component'
-): ManifestStatusFileResolution | null {
-  if (status < 400 || status > 599) {
-    return null;
-  }
-
-  if (format === 'json') {
-    return resolveJson(status, segments);
-  }
-
-  if (status <= 499) {
-    return resolve4xx(status, segments);
-  }
-
-  return resolve5xx(status, segments);
-}
-
-/**
- * 4xx component fallback chain (three separate passes):
- *   Pass 1 — status files (leaf → root): {status}.tsx → 4xx.tsx
- *   Pass 2 — legacy compat (leaf → root): not-found.tsx / forbidden.tsx / unauthorized.tsx
- *   Pass 3 — error.tsx (leaf → root)
- */
-function resolve4xx(
-  status: number,
-  segments: ReadonlyArray<ManifestSegmentNode>
-): ManifestStatusFileResolution | null {
-  const statusStr = String(status);
-
-  // Pass 1: status files across all segments (leaf → root)
-  for (let i = segments.length - 1; i >= 0; i--) {
-    const segment = segments[i];
-    if (!segment.statusFiles) continue;
-
-    // Exact match first
-    const exact = segment.statusFiles[statusStr];
-    if (exact) {
-      return { file: exact, status, kind: 'exact', segmentIndex: i };
-    }
-
-    // Category catch-all
-    const category = segment.statusFiles['4xx'];
-    if (category) {
-      return { file: category, status, kind: 'category', segmentIndex: i };
-    }
-  }
-
-  // Pass 2: legacy compat files (leaf → root)
-  for (let i = segments.length - 1; i >= 0; i--) {
-    const segment = segments[i];
-    if (!segment.legacyStatusFiles) continue;
-
-    for (const [name, legacyStatus] of Object.entries(LEGACY_FILE_TO_STATUS)) {
-      if (legacyStatus === status) {
-        const file = segment.legacyStatusFiles[name];
-        if (file) {
-          return { file, status, kind: 'legacy', segmentIndex: i };
-        }
-      }
-    }
-  }
-
-  // Pass 3: error.tsx (leaf → root)
-  for (let i = segments.length - 1; i >= 0; i--) {
-    if (segments[i].error) {
-      return { file: segments[i].error!, status, kind: 'error', segmentIndex: i };
-    }
-  }
-
-  return null;
-}
-
-/**
- * 5xx component fallback chain (single pass, per-segment):
- *   At each segment (leaf → root): {status}.tsx → 5xx.tsx → error.tsx
- */
-function resolve5xx(
-  status: number,
-  segments: ReadonlyArray<ManifestSegmentNode>
-): ManifestStatusFileResolution | null {
-  const statusStr = String(status);
-
-  for (let i = segments.length - 1; i >= 0; i--) {
-    const segment = segments[i];
-
-    if (segment.statusFiles) {
-      const exact = segment.statusFiles[statusStr];
-      if (exact) {
-        return { file: exact, status, kind: 'exact', segmentIndex: i };
-      }
-
-      const categoryKey = '5xx';
-      const category = segment.statusFiles[categoryKey];
-      if (category) {
-        return { file: category, status, kind: 'category', segmentIndex: i };
-      }
-    }
-
-    if (segment.error) {
-      return { file: segment.error, status, kind: 'error', segmentIndex: i };
-    }
-  }
-
-  return null;
-}
-
-/**
- * JSON fallback chain (for both 4xx and 5xx):
- *   At each segment (leaf → root): {status}.json → {category}.json
- *   No legacy compat, no error.tsx — JSON chain terminates at category catch-all.
- */
-function resolveJson(
-  status: number,
-  segments: ReadonlyArray<ManifestSegmentNode>
-): ManifestStatusFileResolution | null {
-  const statusStr = String(status);
-  const categoryKey = status >= 500 ? '5xx' : '4xx';
-
-  for (let i = segments.length - 1; i >= 0; i--) {
-    const segment = segments[i];
-    if (!segment.jsonStatusFiles) continue;
-
-    const exact = segment.jsonStatusFiles[statusStr];
-    if (exact) {
-      return { file: exact, status, kind: 'exact', segmentIndex: i };
-    }
-
-    const category = segment.jsonStatusFiles[categoryKey];
-    if (category) {
-      return { file: category, status, kind: 'category', segmentIndex: i };
-    }
-  }
-
-  return null;
-}

package/src/server/page-deny-boundary.tsx

@@ -1,56 +0,0 @@
-/**
- * PageDenyBoundary — catches DenySignal from page components server-side.
- *
- * Wraps a server component page by calling it as an async function (the same
- * thing React Flight does internally). If the page throws DenySignal, the
- * boundary catches it and renders the matching deny page as a normal element.
- * No error reaches React Flight — the Flight stream is clean, SSR succeeds,
- * and the entire request uses a single renderToReadableStream call.
- *
- * Client component pages ('use client') are NOT wrapped — they can't call
- * deny() (server-only API) and must go through createElement normally.
- *
- * See design/04-authorization.md, design/10-error-handling.md, TIM-666.
- */
-
-import { DenySignal } from './primitives.js';
-import type { DenyPageEntry } from './deny-page-resolver.js';
-import { renderMatchingDenyPage, setDenyStatus } from './deny-page-resolver.js';
-import { withSpan } from './tracing.js';
-
-/**
- * Async server component that wraps a page call with DenySignal catching.
- *
- * Calls the page component as an async function, awaits it, and catches
- * DenySignal. On catch, renders the deny page in-tree. On success, returns
- * the page's rendered output normally.
- */
-export async function PageDenyBoundary({
-  Page,
-  route,
-  denyPages,
-}: {
-  /** The page server component function. */
-  Page: (...args: unknown[]) => unknown;
-  /** Route path for OTEL tracing. */
-  route: string;
-  /** Deny page fallback chain from the segment chain. */
-  denyPages: DenyPageEntry[];
-}): Promise<React.ReactElement> {
-  try {
-    // Call the page as an async function — same as React Flight does.
-    // Wrap in OTEL span for tracing (replaces the TracedPage wrapper).
-    const result = await withSpan('timber.page', { 'timber.route': route }, () => Page({}));
-    return result as React.ReactElement;
-  } catch (error: unknown) {
-    if (error instanceof DenySignal) {
-      const denyElement = renderMatchingDenyPage(denyPages, error.status, error.data);
-      if (denyElement) {
-        setDenyStatus(error.status);
-        return denyElement;
-      }
-    }
-    // Non-deny errors (RedirectSignal, runtime errors) propagate normally.
-    throw error;
-  }
-}