@timber-js/app 0.2.0-alpha.21 → 0.2.0-alpha.210

package/src/client/types.ts

@@ -1,21 +0,0 @@
-/**
- * A value that is safe to pass through `JSON.stringify` without data loss.
- *
- * Mirrors the server-side type. Defined separately to avoid importing server
- * modules into the client bundle.
- */
-export type JsonSerializable =
-  | string
-  | number
-  | boolean
-  | null
-  | JsonSerializable[]
-  | { [key: string]: JsonSerializable };
-
-export interface RenderErrorDigest<
-  Code extends string = string,
-  Data extends JsonSerializable = JsonSerializable,
-> {
-  code: Code;
-  data: Data;
-}

package/src/client/use-navigation-pending.ts

@@ -1,38 +0,0 @@
-// useNavigationPending — returns true while an RSC navigation is in flight.
-// See design/19-client-navigation.md §"useNavigationPending()"
-//
-// Reads from PendingNavigationContext (provided by TransitionRoot) so the
-// pending state shows immediately (urgent update) and clears atomically
-// with the new tree (same startTransition commit).
-
-import { usePendingNavigationUrl } from './navigation-context.js';
-
-/**
- * Returns true while an RSC navigation is in flight.
- *
- * The pending state is true from the moment the RSC fetch starts until
- * React reconciliation completes. This includes the fetch itself,
- * RSC stream parsing, and React tree reconciliation.
- *
- * It does NOT include Suspense streaming after the shell — only the
- * initial shell reconciliation.
- *
- * ```tsx
- * 'use client'
- * import { useNavigationPending } from '@timber-js/app/client'
- *
- * export function NavBar() {
- *   const isPending = useNavigationPending()
- *   return (
- *     <nav className={isPending ? 'opacity-50' : ''}>
- *       <Link href="/dashboard">Dashboard</Link>
- *     </nav>
- *   )
- * }
- * ```
- */
-export function useNavigationPending(): boolean {
-  const pendingUrl = usePendingNavigationUrl();
-  // During SSR or outside PendingNavigationProvider, no navigation is pending
-  return pendingUrl !== null;
-}

package/src/client/use-params.ts

@@ -1,141 +0,0 @@
-/**
- * useParams() — client-side hook for accessing route params.
- *
- * Returns the dynamic route parameters for the current URL.
- * When called with a route pattern argument, TypeScript narrows
- * the return type to the exact params shape for that route.
- *
- * Two layers of type narrowing work together:
- * 1. The generic overload here uses the Routes interface directly —
- *    `useParams<R>()` returns `Routes[R]['params']`.
- * 2. Build-time codegen generates per-route string-literal overloads
- *    in the .d.ts file for IDE autocomplete (see routing/codegen.ts).
- *
- * When the Routes interface is empty (no codegen yet), the generic
- * overload has `keyof Routes = never`, so only the fallback matches.
- *
- * During SSR, params are read from the ALS-backed SSR data context
- * (populated by ssr-entry.ts) to ensure correct per-request isolation
- * across concurrent requests with streaming Suspense.
- *
- * Reactivity: On the client, useParams() reads from NavigationContext
- * which is updated atomically with the RSC tree render. This replaces
- * the previous useSyncExternalStore approach that suffered from a
- * timing gap between tree render and store notification — causing
- * preserved layout components to briefly show stale active state.
- *
- * All mutable state is delegated to client/state.ts for singleton guarantees.
- * See design/18-build-system.md §"Singleton State Registry"
- *
- * Design doc: design/09-typescript.md §"Typed Routes"
- */
-
-import type { Routes } from '#/index.js';
-import { getSsrData } from './ssr-data.js';
-import { currentParams, _setCurrentParams, paramsListeners } from './state.js';
-import { useNavigationContext } from './navigation-context.js';
-
-// ---------------------------------------------------------------------------
-// Module-level subscribe/notify pattern — kept for backward compat and tests
-// ---------------------------------------------------------------------------
-
-/**
- * Subscribe to params changes.
- * Retained for backward compatibility with tests that verify the
- * subscribe/notify contract. On the client, useParams() reads from
- * NavigationContext instead.
- */
-export function subscribe(callback: () => void): () => void {
-  paramsListeners.add(callback);
-  return () => paramsListeners.delete(callback);
-}
-
-/**
- * Get the current params snapshot (module-level fallback).
- * Used by tests and by the hook when called outside a React component.
- */
-export function getSnapshot(): Record<string, string | string[]> {
-  return currentParams;
-}
-
-// ---------------------------------------------------------------------------
-// Framework API — called by the segment router on each navigation
-// ---------------------------------------------------------------------------
-
-/**
- * Set the current route params in the module-level store.
- *
- * Called by the router on each navigation. This updates the fallback
- * snapshot used by tests and by the hook when called outside a React
- * component (no NavigationContext available).
- *
- * On the client, the primary reactivity path is NavigationContext —
- * the router calls setNavigationState() then renderRoot() which wraps
- * the element in NavigationProvider. setCurrentParams is still called
- * for the module-level fallback.
- *
- * During SSR, params are also available via getSsrData().params
- * (ALS-backed).
- */
-export function setCurrentParams(params: Record<string, string | string[]>): void {
-  _setCurrentParams(params);
-}
-
-/**
- * Notify all legacy subscribers that params have changed.
- *
- * Retained for backward compatibility with tests. On the client,
- * the NavigationContext + renderRoot pattern replaces this — params
- * update atomically with the tree render, so explicit notification
- * is no longer needed.
- */
-export function notifyParamsListeners(): void {
-  for (const listener of paramsListeners) {
-    listener();
-  }
-}
-
-// ---------------------------------------------------------------------------
-// Public hook
-// ---------------------------------------------------------------------------
-
-/**
- * Read the current route's dynamic params.
- *
- * The optional `_route` argument exists only for TypeScript narrowing —
- * it does not affect the runtime return value.
- *
- * On the client, reads from NavigationContext (provided by
- * NavigationProvider in renderRoot). This ensures params update
- * atomically with the RSC tree — no timing gap.
- *
- * During SSR, reads from the ALS-backed SSR data context to ensure
- * per-request isolation across concurrent requests with streaming Suspense.
- *
- * When called outside a React component (e.g., in test assertions),
- * falls back to the module-level snapshot.
- *
- * @overload Typed — when a known route path is passed, returns the
- *   exact params shape from the generated Routes interface.
- * @overload Fallback — returns the generic params record.
- */
-export function useParams<R extends keyof Routes>(route: R): Routes[R]['params'];
-export function useParams(route?: string): Record<string, string | string[]>;
-export function useParams(_route?: string): Record<string, string | string[]> {
-  // Try reading from NavigationContext (client-side, inside React tree).
-  // During SSR, no NavigationProvider is mounted, so this returns null.
-  // When called outside a React component, useContext throws — caught below.
-  try {
-    const navContext = useNavigationContext();
-    if (navContext !== null) {
-      return navContext.params;
-    }
-  } catch {
-    // No React dispatcher available (called outside a component).
-    // Fall through to module-level snapshot below.
-  }
-
-  // SSR path: read from ALS-backed SSR data context.
-  // Falls back to module-level currentParams for tests.
-  return getSsrData()?.params ?? currentParams;
-}

package/src/content/index.ts

@@ -1,13 +0,0 @@
-/**
- * @timber-js/app/content — Public API for content collections.
- *
- * Re-exports from content-collections and provides timber-specific utilities.
- * Users can import directly from 'content-collections' for generated types,
- * or use this module for the re-exports.
- *
- * Design doc: 20-content-collections.md §"Querying Collections"
- */
-
-// Re-export defineCollection and defineConfig for convenience.
-// Users can also import these directly from @content-collections/core.
-export { defineCollection, defineConfig } from '@content-collections/core';

package/src/plugins/adapter-build.ts

@@ -1,118 +0,0 @@
-/**
- * timber-adapter-build — Invoke the adapter's buildOutput after vite build.
- *
- * After all environments are built and the RSC plugin has written its
- * asset manifests, calls `adapter.buildOutput()` to transform the output
- * into a deployable artifact (e.g., Cloudflare Workers entry + wrangler.jsonc).
- *
- * Uses a `buildApp` hook with `order: 'post'` so that Vite calls the
- * RSC plugin's buildApp (which orchestrates all environment builds and
- * writes asset manifests) first, then runs this handler after everything
- * is complete.
- *
- * Design docs: design/11-platform.md, design/25-production-deployments.md
- */
-
-import type { Plugin } from 'vite';
-import { join } from 'node:path';
-import { readFile, writeFile } from 'node:fs/promises';
-import type { PluginContext } from '#/index.js';
-import type { TimberPlatformAdapter, TimberConfig } from '#/adapters/types.js';
-
-export function timberAdapterBuild(ctx: PluginContext): Plugin {
-  return {
-    name: 'timber-adapter-build',
-
-    // order: 'post' causes Vite to run configBuilder.buildApp() (which
-    // includes the RSC plugin's buildApp) before calling this handler.
-    // By the time we run, all environments are built and asset manifests
-    // are written — safe to copy the output.
-    buildApp: {
-      order: 'post' as const,
-      async handler() {
-        if (ctx.dev) return;
-
-        const adapter = ctx.config.adapter as TimberPlatformAdapter | undefined;
-        if (!adapter || typeof adapter.buildOutput !== 'function') return;
-
-        const buildDir = join(ctx.root, 'dist');
-
-        // Serialize the build manifest as a JS module that sets the global.
-        // The adapter writes this as _timber-manifest-init.mjs and imports it
-        // before the RSC handler, so globalThis.__TIMBER_BUILD_MANIFEST__ is
-        // available when virtual:timber-build-manifest evaluates.
-        let manifestInit: string | undefined;
-        if (ctx.buildManifest) {
-          // Strip JS/modulepreload from manifest when client JS is disabled —
-          // those files aren't served, so hints for them are useless.
-          const manifest = ctx.clientJavascript.disabled
-            ? { ...ctx.buildManifest, js: {}, modulepreload: {} }
-            : ctx.buildManifest;
-          const json = JSON.stringify(manifest);
-          manifestInit = `globalThis.__TIMBER_BUILD_MANIFEST__ = ${json};\n`;
-        }
-
-        // Strip JS from the RSC plugin's assets manifest when client JS
-        // is disabled. The RSC plugin writes __vite_rsc_assets_manifest.js
-        // with clientReferenceDeps containing JS URLs — used to inject
-        // <link rel="modulepreload"> tags. Must happen before the adapter
-        // copies files to the output directory.
-        if (ctx.clientJavascript.disabled) {
-          await stripJsFromRscAssetsManifests(buildDir);
-        }
-
-        const adapterConfig: TimberConfig = {
-          output: ctx.config.output ?? 'server',
-          clientJavascriptDisabled: ctx.clientJavascript.disabled,
-          manifestInit,
-        };
-
-        await adapter.buildOutput(adapterConfig, buildDir);
-      },
-    },
-  };
-}
-
-/**
- * Strip JS references from the RSC plugin's assets manifest files.
- *
- * The RSC plugin writes `__vite_rsc_assets_manifest.js` to rsc/ and ssr/
- * as standalone files (not Rollup chunks), so generateBundle can't
- * intercept them. This rewrites the files on disk after all builds
- * complete but before the adapter copies them to the output directory.
- */
-async function stripJsFromRscAssetsManifests(buildDir: string): Promise<void> {
-  const manifestName = '__vite_rsc_assets_manifest.js';
-  const paths = [join(buildDir, 'rsc', manifestName), join(buildDir, 'ssr', manifestName)];
-
-  for (const path of paths) {
-    let content: string;
-    try {
-      content = await readFile(path, 'utf-8');
-    } catch {
-      continue;
-    }
-
-    const jsonStr = content.replace(/^export default\s*/, '').replace(/;?\s*$/, '');
-    let manifest: Record<string, unknown>;
-    try {
-      manifest = JSON.parse(jsonStr);
-    } catch {
-      continue;
-    }
-
-    // Clear JS from clientReferenceDeps — preserves CSS
-    const deps = manifest.clientReferenceDeps as
-      | Record<string, { js: string[]; css: string[] }>
-      | undefined;
-    if (deps) {
-      for (const entry of Object.values(deps)) {
-        entry.js = [];
-      }
-    }
-
-    manifest.bootstrapScriptContent = '';
-
-    await writeFile(path, `export default ${JSON.stringify(manifest, null, 2)};\n`);
-  }
-}

package/src/plugins/cache-transform.ts

@@ -1,199 +0,0 @@
-import type { Plugin } from 'vite';
-import { findFunctionsWithDirective, containsDirective } from '#/utils/directive-parser.js';
-
-/**
- * Parse a cacheLife duration string to seconds.
- * Supports: '30s', '5m', '1h', '2d', '1w', or a plain number (seconds).
- */
-export function parseCacheLife(value: string | number): number {
-  if (typeof value === 'number') return value;
-
-  const match = value.match(/^(\d+)(s|m|h|d|w)$/);
-  if (!match) {
-    throw new Error(
-      `Invalid cacheLife value: "${value}". Expected format: "30s", "5m", "1h", "2d", "1w", or a number.`
-    );
-  }
-
-  const amount = parseInt(match[1], 10);
-  const unit = match[2];
-  const multipliers: Record<string, number> = { s: 1, m: 60, h: 3600, d: 86400, w: 604800 };
-  return amount * multipliers[unit];
-}
-
-// Default TTL when no cacheLife() is specified (Infinity means cache until explicit invalidation).
-const DEFAULT_TTL = Infinity;
-
-export interface CacheTransformWarning {
-  message: string;
-  functionName: string;
-}
-
-interface TransformResult {
-  code: string;
-  map?: null;
-  warnings?: CacheTransformWarning[];
-}
-
-/**
- * Match cacheLife() calls: cacheLife('1h'), cacheLife("5m"), cacheLife(300)
- */
-const CACHE_LIFE_PATTERN = /cacheLife\(\s*(?:'([^']+)'|"([^"]+)"|(\d+))\s*\)/;
-
-/**
- * Strip the 'use cache' directive and cacheLife() call from a function body.
- * Returns the cleaned body and the extracted TTL.
- */
-function extractCacheDirectives(body: string): { cleanBody: string; ttl: number } {
-  let ttl = DEFAULT_TTL;
-
-  // Remove 'use cache' / "use cache" directive (including optional semicolon and newline)
-  let cleanBody = body.replace(/\s*['"]use cache['"];?\s*\n?/, '\n');
-
-  // Extract and remove cacheLife() calls
-  const lifeMatch = cleanBody.match(CACHE_LIFE_PATTERN);
-  if (lifeMatch) {
-    const value = lifeMatch[1] || lifeMatch[2] || parseInt(lifeMatch[3], 10);
-    ttl = parseCacheLife(value);
-    cleanBody = cleanBody.replace(/\s*cacheLife\([^)]*\);?\s*\n?/, '\n');
-  }
-
-  return { cleanBody, ttl };
-}
-
-/**
- * Determine if a function name is a React component (PascalCase).
- */
-function isComponentName(name: string): boolean {
-  return /^[A-Z]/.test(name);
-}
-
-/**
- * Pattern matching page/layout file conventions in a dynamic route segment.
- * Matches paths like: app/[slug]/page.tsx, app/[id]/layout.ts, etc.
- */
-const DYNAMIC_ROUTE_PAGE_PATTERN = /\/\[[^\]]+\].*\/(page|layout)\.[jt]sx?$/;
-
-/**
- * Detect if a function declaration has Promise-typed parameters.
- *
- * Checks for common patterns:
- * - `params: Promise<...>`
- * - `{ params }: { params: Promise<...> }`
- * - `props: { params: Promise<...> }`
- */
-const PROMISE_PARAMS_PATTERN = /params\s*(?::|.*?:)\s*Promise\s*</;
-
-/**
- * Check if a 'use cache' function in a dynamic route page/layout receives
- * Promise-typed params, which are not serializable as cache keys.
- */
-export function detectPromiseParamsWarning(
-  declaration: string,
-  functionName: string,
-  fileId: string
-): CacheTransformWarning | null {
-  if (!DYNAMIC_ROUTE_PAGE_PATTERN.test(fileId)) return null;
-  if (!PROMISE_PARAMS_PATTERN.test(declaration)) return null;
-
-  return {
-    message:
-      `'use cache' on "${functionName}" in "${fileId}" receives Promise params. ` +
-      `Promise is not serializable as a cache key and will cause runtime errors. ` +
-      `Either remove 'use cache' or await the params before using them in a separate cached function.`,
-    functionName,
-  };
-}
-
-/**
- * Transform source code containing 'use cache' directives into
- * registerCachedFunction() calls.
- *
- * Returns null if no transformations were made.
- */
-export function transformUseCache(code: string, fileId: string): TransformResult | null {
-  if (!containsDirective(code, 'use cache')) return null;
-
-  const functions = findFunctionsWithDirective(code, 'use cache');
-  if (functions.length === 0) return null;
-
-  let result = code;
-  let needsImport = false;
-  const warnings: CacheTransformWarning[] = [];
-
-  // Process functions from end to start (sorted descending by start position)
-  for (const fn of functions) {
-    // Warn if function receives Promise params in a dynamic route page/layout
-    const promiseWarning = detectPromiseParamsWarning(fn.declaration, fn.name, fileId);
-    if (promiseWarning) warnings.push(promiseWarning);
-    const { cleanBody, ttl } = extractCacheDirectives(fn.bodyContent);
-    const stableId = `${fileId}#${fn.name}`;
-    const isComponent = isComponentName(fn.name);
-
-    // Build the options object
-    const optsParts = [`ttl: ${ttl === Infinity ? 'Infinity' : ttl}`];
-    optsParts.push(`id: '${stableId}'`);
-    if (isComponent) {
-      optsParts.push('isComponent: true');
-    }
-    const optsStr = `{ ${optsParts.join(', ')} }`;
-
-    // Build the replacement
-    let replacement: string;
-    if (fn.isArrow) {
-      // const Name = async (...) => { body } → const Name = registerCachedFunction(async (...) => { body }, opts)
-      const arrowSig = fn.declaration.replace(/^(?:const|let|var)\s+\w+\s*=\s*/, '');
-      replacement = `const ${fn.name} = registerCachedFunction(${arrowSig} {${cleanBody}}, ${optsStr})`;
-    } else {
-      // async function Name(...) { body } → const Name = registerCachedFunction(async function Name(...) { body }, opts)
-      const fnDecl = fn.declaration.replace(/^(?:export\s+default\s+|export\s+)?/, '');
-      const exportPrefix = fn.prefix.includes('default')
-        ? 'export default '
-        : fn.prefix.includes('export')
-          ? 'export '
-          : '';
-
-      replacement = `${exportPrefix}const ${fn.name} = registerCachedFunction(${fnDecl} {${cleanBody}}, ${optsStr})`;
-    }
-
-    result = result.slice(0, fn.start) + replacement + result.slice(fn.end);
-    needsImport = true;
-  }
-
-  if (needsImport) {
-    // Add the import at the top of the file
-    result = `import { registerCachedFunction } from '@timber-js/app/cache';\n` + result;
-  }
-
-  return { code: result, map: null, warnings: warnings.length > 0 ? warnings : undefined };
-}
-
-/**
- * Vite plugin: timber-cache
- *
- * Transforms 'use cache' directives into registerCachedFunction() calls.
- * Only runs in the RSC environment.
- */
-export function cacheTransformPlugin(): Plugin {
-  return {
-    name: 'timber-cache',
-
-    transform(code, id) {
-      // Only transform in RSC environment
-      // Skip node_modules and non-JS/TS files
-      if (id.includes('node_modules')) return null;
-      if (!/\.[jt]sx?$/.test(id)) return null;
-
-      // Quick bail-out: no 'use cache' directive in this file
-      if (!containsDirective(code, 'use cache')) return null;
-
-      const result = transformUseCache(code, id);
-      if (result?.warnings) {
-        for (const w of result.warnings) {
-          this.warn(`[timber] ${w.message}`);
-        }
-      }
-      return result;
-    },
-  };
-}

package/src/plugins/dynamic-transform.ts

@@ -1,161 +0,0 @@
-/**
- * timber-dynamic-transform — Vite sub-plugin for 'use dynamic' directive.
- *
- * Detects `'use dynamic'` directives in server component function bodies
- * and transforms them into `markDynamic()` runtime calls. The directive
- * declares a dynamic boundary — the component and its subtree opt out of
- * the pre-rendered shell and render per-request.
- *
- * - In `output: 'static'` mode, `'use dynamic'` is a build error.
- * - In standard SSR routes (no prerender.ts), the directive is a no-op
- *   (everything is already per-request), but the transform still runs
- *   so the runtime can skip unnecessary work.
- *
- * Design doc: design/15-future-prerendering.md §"'use dynamic'"
- */
-
-import type { Plugin } from 'vite';
-import type { PluginContext } from '#/index.js';
-import { findFunctionsWithDirective, containsDirective } from '#/utils/directive-parser.js';
-
-// ---------------------------------------------------------------------------
-// Detection
-// ---------------------------------------------------------------------------
-
-/**
- * Quick check: does this source file contain 'use dynamic' anywhere?
- * Used as a fast bail-out before doing expensive AST parsing.
- */
-export function containsUseDynamic(code: string): boolean {
-  return containsDirective(code, 'use dynamic');
-}
-
-// ---------------------------------------------------------------------------
-// Transform
-// ---------------------------------------------------------------------------
-
-interface TransformResult {
-  code: string;
-  map?: null;
-}
-
-/**
- * Find function declarations/expressions containing 'use dynamic' and
- * transform them into markDynamic() calls.
- *
- * Input:
- * ```tsx
- * export default async function AddToCartButton({ productId }) {
- *   'use dynamic'
- *   const user = await getUser()
- *   return <button>Add to cart</button>
- * }
- * ```
- *
- * Output:
- * ```tsx
- * import { markDynamic as __markDynamic } from '@timber-js/app/runtime';
- * export default async function AddToCartButton({ productId }) {
- *   __markDynamic();
- *   const user = await getUser()
- *   return <button>Add to cart</button>
- * }
- * ```
- *
- * The markDynamic() call registers the component boundary as dynamic
- * at render time. The pre-render pass uses this to know which subtrees
- * to skip and leave as holes for per-request rendering.
- */
-export function transformUseDynamic(code: string): TransformResult | null {
-  if (!containsUseDynamic(code)) return null;
-
-  const functions = findFunctionsWithDirective(code, 'use dynamic');
-  if (functions.length === 0) return null;
-
-  // Replace directive strings with __markDynamic() calls, processing
-  // from end to start to preserve source offsets
-  let result = code;
-  for (const fn of functions) {
-    // Replace the directive in the body content
-    const cleanBody = fn.bodyContent.replace(/['"]use dynamic['"];?/, '__markDynamic();');
-    // Reconstruct: replace the body content between braces
-    result = result.slice(0, fn.bodyStart) + cleanBody + result.slice(fn.bodyEnd);
-  }
-
-  // Add the import at the top
-  result = `import { markDynamic as __markDynamic } from '@timber-js/app/runtime';\n` + result;
-
-  return { code: result, map: null };
-}
-
-// ---------------------------------------------------------------------------
-// Static mode validation
-// ---------------------------------------------------------------------------
-
-/**
- * In `output: 'static'` mode, `'use dynamic'` is a build error.
- * Static mode renders everything at build time — there is no per-request
- * rendering to opt into.
- */
-export function validateNoDynamicInStaticMode(
-  code: string
-): { message: string; line?: number } | null {
-  if (!containsUseDynamic(code)) return null;
-
-  const functions = findFunctionsWithDirective(code, 'use dynamic');
-  if (functions.length === 0) return null;
-
-  return {
-    message:
-      `'use dynamic' cannot be used in static mode (output: 'static'). ` +
-      `Static mode renders all content at build time — there is no per-request rendering. ` +
-      `Remove the directive or switch to output: 'server'.`,
-    line: functions[functions.length - 1].directiveLine, // First occurrence (sorted descending)
-  };
-}
-
-// ---------------------------------------------------------------------------
-// Vite Plugin
-// ---------------------------------------------------------------------------
-
-/**
- * Create the timber-dynamic-transform Vite plugin.
- *
- * In server mode: transforms 'use dynamic' into markDynamic() calls.
- * In static mode: rejects 'use dynamic' as a build error.
- */
-export function timberDynamicTransform(ctx: PluginContext): Plugin {
-  const isStatic = ctx.config.output === 'static';
-
-  return {
-    name: 'timber-dynamic-transform',
-
-    transform(code: string, id: string) {
-      // Skip node_modules
-      if (id.includes('node_modules')) return null;
-
-      // Only check files in the app directory
-      if (!id.includes('/app/') && !id.startsWith('app/')) return null;
-
-      // Only check JS/TS files
-      if (!/\.[jt]sx?$/.test(id)) return null;
-
-      // Quick bail-out
-      if (!containsUseDynamic(code)) return null;
-
-      // In static mode, 'use dynamic' is a build error
-      if (isStatic) {
-        const error = validateNoDynamicInStaticMode(code);
-        if (error) {
-          this.error(
-            `[timber] Static mode error in ${id}${error.line ? `:${error.line}` : ''}: ${error.message}`
-          );
-        }
-        return null;
-      }
-
-      // In server mode, transform the directive
-      return transformUseDynamic(code);
-    },
-  };
-}