@farm.js/core 0.1.46 → 0.1.48

package/dist/plugin-DBBZ4JI2.cjs

@@ -1,32 +0,0 @@
-"use strict";Object.defineProperty(exports, "__esModule", {value: true});
-
-
-
-
-var _chunk45QJHGZMcjs = require('./chunk-45QJHGZM.cjs');
-require('./chunk-4U5XZDLG.cjs');
-require('./chunk-6D24SDKO.cjs');
-require('./chunk-TI7UANHI.cjs');
-require('./chunk-FVPXT2JR.cjs');
-
-
-var _chunkYJRZR7VUcjs = require('./chunk-YJRZR7VU.cjs');
-require('./chunk-VEKFLAQM.cjs');
-require('./chunk-CMGMGHUZ.cjs');
-require('./chunk-6QOLZITB.cjs');
-
-
-
-var _chunkPJ42JESYcjs = require('./chunk-PJ42JESY.cjs');
-require('./chunk-4TLUFAIP.cjs');
-require('./chunk-I57LW5VZ.cjs');
-require('./chunk-S3JO3N4H.cjs');
-
-
-
-
-
-
-
-
-exports.FARM_NODE_RESPONSE_END_PENDING = _chunk45QJHGZMcjs.FARM_NODE_RESPONSE_END_PENDING; exports.FarmDevEnvironmentError = _chunkPJ42JESYcjs.FarmDevEnvironmentError; exports.FarmRuntimeShutdownError = _chunk45QJHGZMcjs.FarmRuntimeShutdownError; exports.PluginManager = _chunk45QJHGZMcjs.PluginManager; exports.definePlugin = _chunk45QJHGZMcjs.definePlugin; exports.loadFarmDevModule = _chunkPJ42JESYcjs.loadFarmDevModule; exports.resolveFarmDevtoolsConfig = _chunkYJRZR7VUcjs.resolveFarmDevtoolsConfig;

package/dist/plugin-SYMK7PQ2.mjs

@@ -1,32 +0,0 @@
-import {
-  FARM_NODE_RESPONSE_END_PENDING,
-  FarmRuntimeShutdownError,
-  PluginManager,
-  definePlugin
-} from "./chunk-FGH3ZXTP.mjs";
-import "./chunk-GC3EM6H4.mjs";
-import "./chunk-WDMIW6Q6.mjs";
-import "./chunk-Y5RG6B7S.mjs";
-import "./chunk-CZS6OACQ.mjs";
-import {
-  resolveFarmDevtoolsConfig
-} from "./chunk-JBSVKMC5.mjs";
-import "./chunk-4OOBRCJX.mjs";
-import "./chunk-ONUEYC6N.mjs";
-import "./chunk-H3EGVQE5.mjs";
-import {
-  FarmDevEnvironmentError,
-  loadFarmDevModule
-} from "./chunk-QCVIRVHE.mjs";
-import "./chunk-P7XDC7UJ.mjs";
-import "./chunk-4RB44K6Z.mjs";
-import "./chunk-LPEX4YW6.mjs";
-export {
-  FARM_NODE_RESPONSE_END_PENDING,
-  FarmDevEnvironmentError,
-  FarmRuntimeShutdownError,
-  PluginManager,
-  definePlugin,
-  loadFarmDevModule,
-  resolveFarmDevtoolsConfig
-};

package/dist/production-runtime-BEbIyIUe.d.mts

@@ -1,123 +0,0 @@
-import { aD as ReadonlyMiddlewareStore, aE as FarmMiddlewareConfig, aF as MiddlewareModule, aG as MiddlewareConfig, aH as MiddlewareContext } from './client-plugins-DEmIQo5R.mjs';
-import { R as ResolvedFarmI18nConfig } from './types--Wh02r5_.mjs';
-import { R as ResolvedFarmServerConfig } from './workflows-Df1C_7OG.mjs';
-
-/**
- * Server-side middleware utilities for accessing middleware data in pages
- */
-
-type MiddlewareStoreInput = Record<string, any> | Map<string, any>;
-/**
- * Internal: Run code with middleware data available
- * This is called by the server renderer
- */
-declare function _runWithMiddlewareData<T>(data: MiddlewareStoreInput, fn: () => T | Promise<T>): Promise<T>;
-/** Internal: Run code with server-only middleware context available. */
-declare function _runWithMiddlewareContext<T>(context: MiddlewareStoreInput, fn: () => T | Promise<T>): Promise<T>;
-/**
- * Get middleware data in a server component
- * No props needed - uses global storage!
- *
- * @example
- * ```tsx
- * import { getMiddlewareData } from 'farm/middleware';
- *
- * export default function Page() {
- *   const data = getMiddlewareData();  // ← No props needed!
- *   const user = data.get('user');
- *   const demoInfo = data.get('demoInfo');
- *
- *   return <div>Welcome {user?.name}</div>;
- * }
- * ```
- */
-declare function getMiddlewareData<T extends Record<string, any> = Record<string, any>>(): Map<keyof T, T[keyof T]>;
-/**
- * Get a specific value from middleware data (synchronous)
- * Uses AsyncLocalStorage for request scoping - no props needed.
- *
- * @example
- * ```tsx
- * import { getMiddlewareValue } from 'farm/middleware';
- *
- * export default function Page() {
- *   const user = getMiddlewareValue<User>('user');  // ← No props needed!
- *   const stats = getMiddlewareValue('dashboardStats');
- *
- *   return <div>Welcome {user?.name}</div>;
- * }
- * ```
- */
-declare function getMiddlewareValue<T = any>(key: string): T | undefined;
-/**
- * Read server-only values set by route middleware for the current request.
- * The returned store is available to the matched page, layouts, and nested
- * Server Components, but is never added to hydration props.
- */
-declare function getMiddlewareContext<T extends Record<string, any> = Record<string, any>>(): ReadonlyMiddlewareStore<T>;
-
-interface ProductionMiddlewareModuleEntry {
-    path: string;
-    filePath?: string;
-    module: MiddlewareModule | Record<string, any>;
-}
-interface ProductionMiddlewareRunnerOptions {
-    config?: FarmMiddlewareConfig | null;
-    modules?: ProductionMiddlewareModuleEntry[];
-    i18n?: ResolvedFarmI18nConfig;
-    server?: Pick<ResolvedFarmServerConfig, "trustProxy">;
-    /** The app's public API path (`api.basePath`); `/api` middleware guards it too. */
-    apiBasePath?: string;
-    /**
-     * @internal The app matches pages against the request path as received, without stripping
-     * basePath or locale (the RSC entry), so middleware matches that path too.
-     */
-    rawPathRouting?: boolean;
-}
-interface ProductionMiddlewareRequestOptions {
-    /**
-     * The address of the peer that opened the connection, as the server adapter
-     * reports it. A web Request carries no socket, so this is the only way a
-     * built app's middleware learns the client address it already has in
-     * development. A trusted proxy's `x-forwarded-for` still takes precedence.
-     */
-    clientAddress?: string;
-}
-interface ProductionMiddlewareResult {
-    request: Request;
-    response: Response | null;
-    data: Map<string, any>;
-    context: Map<string, any>;
-    headers: Headers;
-    handled: boolean;
-    /**
-     * Middleware without `cache: "public"` ran and let the request through. It may have been a
-     * guard (an IP allowlist, an API key header), so the response must not reach a shared cache.
-     */
-    guarded: boolean;
-    /** Middleware called notFound(): answer with the app's not-found page. */
-    notFound?: true;
-}
-/**
- * Decide whether a middleware entry's `export const config` applies to a path.
- *
- * Exported so the standalone dev plugin matches exactly what the production
- * runner does instead of maintaining a parallel implementation.
- */
-declare function matchesMiddlewareConfig(pathname: string, config: MiddlewareConfig, ctx: MiddlewareContext): {
-    matched: boolean;
-    params?: Record<string, string>;
-};
-declare function createProductionMiddlewareRunner(options?: ProductionMiddlewareRunnerOptions): (request: Request, requestOptions?: ProductionMiddlewareRequestOptions) => Promise<ProductionMiddlewareResult>;
-declare function applyProductionMiddlewareHeaders(response: Response, middlewareHeaders?: Headers | null): Response;
-/**
- * Keep a response that middleware let through out of shared caches. A CDN keys its copy by URL
- * and serves it without running the guard again, so a page an IP allowlist or API key header
- * let one visitor read would reach everyone. A Cache-Control that a shared cache may store
- * becomes `private, no-store`; a private one is left as it is.
- *
- * @internal
- */
-declare function _withFarmGuardedResponseCache(response: Response): Response;
-
-export { _runWithMiddlewareContext as _, _runWithMiddlewareData as a, applyProductionMiddlewareHeaders as b, createProductionMiddlewareRunner as c, getMiddlewareData as d, getMiddlewareValue as e, _withFarmGuardedResponseCache as f, getMiddlewareContext as g, matchesMiddlewareConfig as m };

package/dist/production-runtime-DsHjccVI.d.ts

@@ -1,123 +0,0 @@
-import { aD as ReadonlyMiddlewareStore, aE as FarmMiddlewareConfig, aF as MiddlewareModule, aG as MiddlewareConfig, aH as MiddlewareContext } from './client-plugins-br48Hpmk.js';
-import { R as ResolvedFarmI18nConfig } from './types--Wh02r5_.js';
-import { R as ResolvedFarmServerConfig } from './workflows-Df1C_7OG.js';
-
-/**
- * Server-side middleware utilities for accessing middleware data in pages
- */
-
-type MiddlewareStoreInput = Record<string, any> | Map<string, any>;
-/**
- * Internal: Run code with middleware data available
- * This is called by the server renderer
- */
-declare function _runWithMiddlewareData<T>(data: MiddlewareStoreInput, fn: () => T | Promise<T>): Promise<T>;
-/** Internal: Run code with server-only middleware context available. */
-declare function _runWithMiddlewareContext<T>(context: MiddlewareStoreInput, fn: () => T | Promise<T>): Promise<T>;
-/**
- * Get middleware data in a server component
- * No props needed - uses global storage!
- *
- * @example
- * ```tsx
- * import { getMiddlewareData } from 'farm/middleware';
- *
- * export default function Page() {
- *   const data = getMiddlewareData();  // ← No props needed!
- *   const user = data.get('user');
- *   const demoInfo = data.get('demoInfo');
- *
- *   return <div>Welcome {user?.name}</div>;
- * }
- * ```
- */
-declare function getMiddlewareData<T extends Record<string, any> = Record<string, any>>(): Map<keyof T, T[keyof T]>;
-/**
- * Get a specific value from middleware data (synchronous)
- * Uses AsyncLocalStorage for request scoping - no props needed.
- *
- * @example
- * ```tsx
- * import { getMiddlewareValue } from 'farm/middleware';
- *
- * export default function Page() {
- *   const user = getMiddlewareValue<User>('user');  // ← No props needed!
- *   const stats = getMiddlewareValue('dashboardStats');
- *
- *   return <div>Welcome {user?.name}</div>;
- * }
- * ```
- */
-declare function getMiddlewareValue<T = any>(key: string): T | undefined;
-/**
- * Read server-only values set by route middleware for the current request.
- * The returned store is available to the matched page, layouts, and nested
- * Server Components, but is never added to hydration props.
- */
-declare function getMiddlewareContext<T extends Record<string, any> = Record<string, any>>(): ReadonlyMiddlewareStore<T>;
-
-interface ProductionMiddlewareModuleEntry {
-    path: string;
-    filePath?: string;
-    module: MiddlewareModule | Record<string, any>;
-}
-interface ProductionMiddlewareRunnerOptions {
-    config?: FarmMiddlewareConfig | null;
-    modules?: ProductionMiddlewareModuleEntry[];
-    i18n?: ResolvedFarmI18nConfig;
-    server?: Pick<ResolvedFarmServerConfig, "trustProxy">;
-    /** The app's public API path (`api.basePath`); `/api` middleware guards it too. */
-    apiBasePath?: string;
-    /**
-     * @internal The app matches pages against the request path as received, without stripping
-     * basePath or locale (the RSC entry), so middleware matches that path too.
-     */
-    rawPathRouting?: boolean;
-}
-interface ProductionMiddlewareRequestOptions {
-    /**
-     * The address of the peer that opened the connection, as the server adapter
-     * reports it. A web Request carries no socket, so this is the only way a
-     * built app's middleware learns the client address it already has in
-     * development. A trusted proxy's `x-forwarded-for` still takes precedence.
-     */
-    clientAddress?: string;
-}
-interface ProductionMiddlewareResult {
-    request: Request;
-    response: Response | null;
-    data: Map<string, any>;
-    context: Map<string, any>;
-    headers: Headers;
-    handled: boolean;
-    /**
-     * Middleware without `cache: "public"` ran and let the request through. It may have been a
-     * guard (an IP allowlist, an API key header), so the response must not reach a shared cache.
-     */
-    guarded: boolean;
-    /** Middleware called notFound(): answer with the app's not-found page. */
-    notFound?: true;
-}
-/**
- * Decide whether a middleware entry's `export const config` applies to a path.
- *
- * Exported so the standalone dev plugin matches exactly what the production
- * runner does instead of maintaining a parallel implementation.
- */
-declare function matchesMiddlewareConfig(pathname: string, config: MiddlewareConfig, ctx: MiddlewareContext): {
-    matched: boolean;
-    params?: Record<string, string>;
-};
-declare function createProductionMiddlewareRunner(options?: ProductionMiddlewareRunnerOptions): (request: Request, requestOptions?: ProductionMiddlewareRequestOptions) => Promise<ProductionMiddlewareResult>;
-declare function applyProductionMiddlewareHeaders(response: Response, middlewareHeaders?: Headers | null): Response;
-/**
- * Keep a response that middleware let through out of shared caches. A CDN keys its copy by URL
- * and serves it without running the guard again, so a page an IP allowlist or API key header
- * let one visitor read would reach everyone. A Cache-Control that a shared cache may store
- * becomes `private, no-store`; a private one is left as it is.
- *
- * @internal
- */
-declare function _withFarmGuardedResponseCache(response: Response): Response;
-
-export { _runWithMiddlewareContext as _, _runWithMiddlewareData as a, applyProductionMiddlewareHeaders as b, createProductionMiddlewareRunner as c, getMiddlewareData as d, getMiddlewareValue as e, _withFarmGuardedResponseCache as f, getMiddlewareContext as g, matchesMiddlewareConfig as m };

package/dist/programmatic-routes-client-DlMKstmL.d.ts

@@ -1,184 +0,0 @@
-import { R as RouteRenderingOptions, D as DirectiveRenderingConfig, a as RouteRenderingConfig } from './route-rendering-DTLNruPw.js';
-import { R as RouteModule, aK as SSGCollectionResult, aL as SSGPage } from './client-plugins-br48Hpmk.js';
-
-/**
- * Farm.js SSG (Static Site Generation) Module
- *
- * Handles collection and pre-rendering of SSG pages at build time.
- *
- * SSR is the default - pages render on each request
- * SSG is opt-in via `export const ssg = true`, Next-compatible route
- * config exports, or a top-of-file rendering directive.
- *
- * @example
- * ```tsx
- * // SSG Page
- * export const ssg = true;
- * export default function AboutPage() {
- *   return <h1>About</h1>;
- * }
- *
- * // SSG with ISR
- * export const ssg = true;
- * export const revalidate = 60;
- * export default async function ProductsPage() {
- *   const products = await fetchProducts();
- *   return <ProductList products={products} />;
- * }
- *
- * // Dynamic SSG
- * export const ssg = true;
- * export async function getStaticPaths() {
- *   const posts = await fetchPosts();
- *   return posts.map(post => ({ slug: post.slug }));
- * }
- * export default async function BlogPost({ params }) {
- *   return <article>{params.slug}</article>;
- * }
- *
- * // Next-compatible route config
- * export const dynamic = "force-static";
- * export const revalidate = 60;
- *
- * // PPR/static-shell route
- * export const experimental_ppr = true;
- * export const revalidate = 60;
- *
- * // Directive config
- * "use ssg; 60";
- * export default function DocsPage() {
- *   return <h1>Docs</h1>;
- * }
- * ```
- */
-
-interface RouteEntry {
-    path: string;
-    filePath: string;
-    isDynamic: boolean;
-    pattern: string;
-}
-
-interface StaticRouteCandidateAnalysis {
-    candidate: boolean;
-    blockers: string[];
-}
-/**
- * Resolve the effective rendering mode. Direct request reads make an explicitly
- * static route dynamic so request-specific HTML cannot enter a shared artifact.
- */
-declare function resolveRouteRenderingConfig(mod: RouteModule | null | undefined, source?: string, options?: RouteRenderingOptions): RouteRenderingConfig;
-declare function resolveRouteRenderingConfigFromFile(mod: RouteModule | null | undefined, filePath: string, options?: RouteRenderingOptions): Promise<RouteRenderingConfig>;
-/**
- * Conservatively identify a route that may be safe to pre-render.
- *
- * This intentionally produces a suggestion rather than changing rendering:
- * request-bound work can live in a transitive import, which source inspection
- * of the route module cannot prove safe. Explicit route config always wins.
- */
-declare function analyzeStaticRouteCandidate(mod: RouteModule | null | undefined, source: string | undefined, options?: {
-    isDynamic?: boolean;
-}): StaticRouteCandidateAnalysis;
-declare function findRequestBoundSourceBlockers(source: string): string[];
-declare function parseRouteRenderingDirective(source: string | undefined): DirectiveRenderingConfig | undefined;
-/**
- * A route's rendering directive as the production runtime needs it: the parsed directive plus
- * whether its source reads request state. The runtime only sees module exports, so the build
- * decides `requestBound` here and bakes it into the generated server entry, where
- * `mergeRouteRenderingDirectiveConfig` combines it with the module's exports.
- */
-declare function readRouteRenderingDirectiveFromFile(modulePath: string): DirectiveRenderingConfig | undefined;
-/**
- * Collect SSG pages from route modules
- *
- * Scans all routes and categorizes them into:
- * - SSG pages: Pre-rendered at build time
- * - SSR routes: Rendered on each request
- *
- * @param routes - Array of route entries
- * @param loadModule - Function to load a route module
- * @returns SSG pages and SSR routes
- */
-declare function collectSSGPages(routes: RouteEntry[], loadModule: (filePath: string) => Promise<RouteModule>, options?: {
-    suggestStaticRendering?: boolean;
-}): Promise<SSGCollectionResult>;
-/**
- * Check if a route module is SSG
- */
-declare function isSSGModule(mod: RouteModule | null | undefined): boolean;
-/**
- * Check if a route module has ISR (Incremental Static Regeneration)
- */
-declare function hasISR(mod: RouteModule | null | undefined): boolean;
-/**
- * Get revalidation interval for a module
- */
-declare function getRevalidateInterval(mod: RouteModule | null | undefined): number | undefined;
-/**
- * Check if a route module has PPR/static-shell caching enabled.
- */
-declare function hasPPR(mod: RouteModule | null | undefined, options?: RouteRenderingOptions): boolean;
-/**
- * Generate SSG manifest for production builds
- */
-declare function generateSSGManifest(pages: SSGPage[]): string;
-/**
- * Check if a URL path matches an SSG page
- */
-declare function matchSSGPage(urlPath: string, ssgPages: SSGPage[]): SSGPage | undefined;
-
-/**
- * The browser copy of a programmatic page or layout imports only the module that defines its
- * component, never the routes file. Guards, data hooks, static paths, generated metadata, API
- * handlers, and whatever the routes file imports for them stay out of the client graph because
- * the client graph never reaches the routes file.
- *
- * Farm already evaluates the routes file on the server to build its route table. That
- * evaluation also tells it where each component lives: the server module graph holds every
- * module the routes file reached, with its exports, so the module that exports the very
- * function (or object) a route uses as its `component` is that component's own module. This
- * works for any way the route list is built (helpers, re-exported lists, assignments, aliases)
- * because it reads the evaluated value instead of the routes file's syntax. A component that no
- * other module exports (declared in the routes file, or computed there) has no module to
- * import, so a client build that needs it fails with an actionable error.
- *
- * A module that holds route definitions is never a component's client import, however it holds
- * them: Farm finds definitions in every evaluated module's exports (inside objects, arrays,
- * maps, and sets), and route factories record the module that called them while routes are
- * evaluated, which also finds definitions kept behind a function. A definition written as an
- * object literal and kept out of every export can't be traced, so then a component module is
- * accepted only when neither it nor anything it imports holds route-defining code.
- */
-type ProgrammaticClientRouteKind = "page" | "layout";
-interface ProgrammaticClientModuleExport {
-    /** Absolute path of the module that exports the value. */
-    file: string;
-    /** The export name that holds it. */
-    exportName: string;
-}
-interface ProgrammaticClientRoute {
-    kind: ProgrammaticClientRouteKind;
-    path: string;
-    /** Absolute path of the routes file that defines the route. */
-    routesFile: string;
-    component?: ProgrammaticClientModuleExport;
-    pending?: ProgrammaticClientModuleExport;
-    /**
-     * The route options the server resolves into the page's props (params, search, guard, data).
-     * The browser copy renders only from props the server resolved.
-     */
-    serverProps?: string[];
-    /** Why the browser copy can't be generated, when it can't. */
-    problem?: string;
-}
-interface ProgrammaticClientRoutes {
-    /** Keyed by {@link programmaticClientRouteKey}. */
-    routes: ReadonlyMap<string, ProgrammaticClientRoute>;
-    /**
-     * Routes files and the modules that export route definitions. None of them may enter the
-     * client graph.
-     */
-    routeSourceFiles: ReadonlySet<string>;
-}
-
-export { type ProgrammaticClientRoutes as P, type StaticRouteCandidateAnalysis as S, analyzeStaticRouteCandidate as a, getRevalidateInterval as b, collectSSGPages as c, hasPPR as d, resolveRouteRenderingConfig as e, findRequestBoundSourceBlockers as f, generateSSGManifest as g, hasISR as h, isSSGModule as i, resolveRouteRenderingConfigFromFile as j, matchSSGPage as m, parseRouteRenderingDirective as p, readRouteRenderingDirectiveFromFile as r };

package/dist/programmatic-routes-client-Dqr6tHND.d.mts

@@ -1,184 +0,0 @@
-import { R as RouteRenderingOptions, D as DirectiveRenderingConfig, a as RouteRenderingConfig } from './route-rendering-Do8tuYgh.mjs';
-import { R as RouteModule, aK as SSGCollectionResult, aL as SSGPage } from './client-plugins-DEmIQo5R.mjs';
-
-/**
- * Farm.js SSG (Static Site Generation) Module
- *
- * Handles collection and pre-rendering of SSG pages at build time.
- *
- * SSR is the default - pages render on each request
- * SSG is opt-in via `export const ssg = true`, Next-compatible route
- * config exports, or a top-of-file rendering directive.
- *
- * @example
- * ```tsx
- * // SSG Page
- * export const ssg = true;
- * export default function AboutPage() {
- *   return <h1>About</h1>;
- * }
- *
- * // SSG with ISR
- * export const ssg = true;
- * export const revalidate = 60;
- * export default async function ProductsPage() {
- *   const products = await fetchProducts();
- *   return <ProductList products={products} />;
- * }
- *
- * // Dynamic SSG
- * export const ssg = true;
- * export async function getStaticPaths() {
- *   const posts = await fetchPosts();
- *   return posts.map(post => ({ slug: post.slug }));
- * }
- * export default async function BlogPost({ params }) {
- *   return <article>{params.slug}</article>;
- * }
- *
- * // Next-compatible route config
- * export const dynamic = "force-static";
- * export const revalidate = 60;
- *
- * // PPR/static-shell route
- * export const experimental_ppr = true;
- * export const revalidate = 60;
- *
- * // Directive config
- * "use ssg; 60";
- * export default function DocsPage() {
- *   return <h1>Docs</h1>;
- * }
- * ```
- */
-
-interface RouteEntry {
-    path: string;
-    filePath: string;
-    isDynamic: boolean;
-    pattern: string;
-}
-
-interface StaticRouteCandidateAnalysis {
-    candidate: boolean;
-    blockers: string[];
-}
-/**
- * Resolve the effective rendering mode. Direct request reads make an explicitly
- * static route dynamic so request-specific HTML cannot enter a shared artifact.
- */
-declare function resolveRouteRenderingConfig(mod: RouteModule | null | undefined, source?: string, options?: RouteRenderingOptions): RouteRenderingConfig;
-declare function resolveRouteRenderingConfigFromFile(mod: RouteModule | null | undefined, filePath: string, options?: RouteRenderingOptions): Promise<RouteRenderingConfig>;
-/**
- * Conservatively identify a route that may be safe to pre-render.
- *
- * This intentionally produces a suggestion rather than changing rendering:
- * request-bound work can live in a transitive import, which source inspection
- * of the route module cannot prove safe. Explicit route config always wins.
- */
-declare function analyzeStaticRouteCandidate(mod: RouteModule | null | undefined, source: string | undefined, options?: {
-    isDynamic?: boolean;
-}): StaticRouteCandidateAnalysis;
-declare function findRequestBoundSourceBlockers(source: string): string[];
-declare function parseRouteRenderingDirective(source: string | undefined): DirectiveRenderingConfig | undefined;
-/**
- * A route's rendering directive as the production runtime needs it: the parsed directive plus
- * whether its source reads request state. The runtime only sees module exports, so the build
- * decides `requestBound` here and bakes it into the generated server entry, where
- * `mergeRouteRenderingDirectiveConfig` combines it with the module's exports.
- */
-declare function readRouteRenderingDirectiveFromFile(modulePath: string): DirectiveRenderingConfig | undefined;
-/**
- * Collect SSG pages from route modules
- *
- * Scans all routes and categorizes them into:
- * - SSG pages: Pre-rendered at build time
- * - SSR routes: Rendered on each request
- *
- * @param routes - Array of route entries
- * @param loadModule - Function to load a route module
- * @returns SSG pages and SSR routes
- */
-declare function collectSSGPages(routes: RouteEntry[], loadModule: (filePath: string) => Promise<RouteModule>, options?: {
-    suggestStaticRendering?: boolean;
-}): Promise<SSGCollectionResult>;
-/**
- * Check if a route module is SSG
- */
-declare function isSSGModule(mod: RouteModule | null | undefined): boolean;
-/**
- * Check if a route module has ISR (Incremental Static Regeneration)
- */
-declare function hasISR(mod: RouteModule | null | undefined): boolean;
-/**
- * Get revalidation interval for a module
- */
-declare function getRevalidateInterval(mod: RouteModule | null | undefined): number | undefined;
-/**
- * Check if a route module has PPR/static-shell caching enabled.
- */
-declare function hasPPR(mod: RouteModule | null | undefined, options?: RouteRenderingOptions): boolean;
-/**
- * Generate SSG manifest for production builds
- */
-declare function generateSSGManifest(pages: SSGPage[]): string;
-/**
- * Check if a URL path matches an SSG page
- */
-declare function matchSSGPage(urlPath: string, ssgPages: SSGPage[]): SSGPage | undefined;
-
-/**
- * The browser copy of a programmatic page or layout imports only the module that defines its
- * component, never the routes file. Guards, data hooks, static paths, generated metadata, API
- * handlers, and whatever the routes file imports for them stay out of the client graph because
- * the client graph never reaches the routes file.
- *
- * Farm already evaluates the routes file on the server to build its route table. That
- * evaluation also tells it where each component lives: the server module graph holds every
- * module the routes file reached, with its exports, so the module that exports the very
- * function (or object) a route uses as its `component` is that component's own module. This
- * works for any way the route list is built (helpers, re-exported lists, assignments, aliases)
- * because it reads the evaluated value instead of the routes file's syntax. A component that no
- * other module exports (declared in the routes file, or computed there) has no module to
- * import, so a client build that needs it fails with an actionable error.
- *
- * A module that holds route definitions is never a component's client import, however it holds
- * them: Farm finds definitions in every evaluated module's exports (inside objects, arrays,
- * maps, and sets), and route factories record the module that called them while routes are
- * evaluated, which also finds definitions kept behind a function. A definition written as an
- * object literal and kept out of every export can't be traced, so then a component module is
- * accepted only when neither it nor anything it imports holds route-defining code.
- */
-type ProgrammaticClientRouteKind = "page" | "layout";
-interface ProgrammaticClientModuleExport {
-    /** Absolute path of the module that exports the value. */
-    file: string;
-    /** The export name that holds it. */
-    exportName: string;
-}
-interface ProgrammaticClientRoute {
-    kind: ProgrammaticClientRouteKind;
-    path: string;
-    /** Absolute path of the routes file that defines the route. */
-    routesFile: string;
-    component?: ProgrammaticClientModuleExport;
-    pending?: ProgrammaticClientModuleExport;
-    /**
-     * The route options the server resolves into the page's props (params, search, guard, data).
-     * The browser copy renders only from props the server resolved.
-     */
-    serverProps?: string[];
-    /** Why the browser copy can't be generated, when it can't. */
-    problem?: string;
-}
-interface ProgrammaticClientRoutes {
-    /** Keyed by {@link programmaticClientRouteKey}. */
-    routes: ReadonlyMap<string, ProgrammaticClientRoute>;
-    /**
-     * Routes files and the modules that export route definitions. None of them may enter the
-     * client graph.
-     */
-    routeSourceFiles: ReadonlySet<string>;
-}
-
-export { type ProgrammaticClientRoutes as P, type StaticRouteCandidateAnalysis as S, analyzeStaticRouteCandidate as a, getRevalidateInterval as b, collectSSGPages as c, hasPPR as d, resolveRouteRenderingConfig as e, findRequestBoundSourceBlockers as f, generateSSGManifest as g, hasISR as h, isSSGModule as i, resolveRouteRenderingConfigFromFile as j, matchSSGPage as m, parseRouteRenderingDirective as p, readRouteRenderingDirectiveFromFile as r };