@farm.js/core 0.1.40 → 0.1.41

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

@@ -1,55 +0,0 @@
-/**
- * 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 };

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

@@ -1,55 +0,0 @@
-/**
- * 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 };