@rangojs/router 0.6.0 → 0.7.0

package/dist/types/client-urls/server-projection.d.ts

@@ -1,6 +1,6 @@
 import type { SearchSchemaValue } from "../search-params.js";
 import type { TrailingSlashMode } from "../types.js";
-import type { UrlPatterns } from "../urls/pattern-types.js";
+import type { PartialPrerenderProps, UrlPatterns } from "../urls/pattern-types.js";
 import type { ClientTransitionConfig, ClientUrlPatterns } from "./types.js";
 export interface ClientUrlReference {
     readonly $$typeof: symbol;
@@ -10,6 +10,15 @@ export type ClientUrlDefinitionSource = ClientUrlReference | ClientUrlPatterns;
 export interface ClientUrlProjectionOptions {
     readonly search?: Readonly<Record<string, SearchSchemaValue>>;
     readonly trailingSlash?: TrailingSlashMode;
+    /**
+     * The `ppr` path option, JSON-projected. Materialization passes it onto
+     * the group route's server `path()` verbatim, so the manifest entry
+     * carries it and the runtime shell capture/serve lanes engage exactly as
+     * for a hand-written server route (search is part of shell identity —
+     * the capture render seeds the key's own search, so group static parts
+     * may read useSearchParams).
+     */
+    readonly ppr?: true | Readonly<PartialPrerenderProps>;
 }
 export interface ClientUrlProjectionRoute {
     readonly id: string;

package/dist/types/client-urls/types.d.ts

@@ -15,7 +15,7 @@ export interface ClientUrlItem {
 export type ClientUrlItemInput = ClientUrlItem | readonly ClientUrlItemInput[];
 export type ClientUrlItems = readonly ClientUrlItemInput[];
 export type ClientUrlUse = () => ClientUrlItems;
-export type ClientPathOptions<TName extends string = string, TSearch extends SearchSchema = SearchSchema> = Pick<PathOptions<TName, TSearch>, "name" | "search" | "trailingSlash">;
+export type ClientPathOptions<TName extends string = string, TSearch extends SearchSchema = SearchSchema> = Pick<PathOptions<TName, TSearch>, "name" | "search" | "trailingSlash" | "ppr">;
 export type ClientPathFn = <const TPattern extends string, const TName extends string = UnnamedRoute, const TSearch extends SearchSchema = {}>(pattern: TPattern, component: ComponentType, optionsOrUse?: ClientPathOptions<TName, TSearch> | ClientUrlUse, use?: ClientUrlUse) => ClientUrlItem & TypedRouteItem<TName, TPattern, unknown, TSearch>;
 export type ClientLayoutFn = <const TItems extends ClientUrlItems>(component: ComponentType, children: () => TItems) => ClientUrlItem & TypedLayoutItem<ExtractRoutes<TItems>>;
 /**
@@ -104,7 +104,10 @@ export interface ClientUrlHelpers {
      * Pass `{ stream: "navigation" }` to await this loader before first flush
      * on DOCUMENT requests (see {@link LoaderOptions}) — the opt-in for loaders
      * whose data, handle pushes, or thrown notFound()/redirect() must be in the
-     * SSR'd HTML. Per-loader: a dynamic sibling keeps streaming.
+     * SSR'd HTML. Per-loader: a dynamic sibling keeps streaming. Under a
+     * `ppr` group route the flag BAKES: the loader executes at shell capture
+     * and its settled return freezes into the shell (nested promises stay
+     * live holes).
      */
     readonly loader: <TData>(definition: LoaderDefinition<TData>, optionsOrUse?: LoaderOptions | ClientUrlUse, use?: ClientUrlUse) => ClientUrlItem;
     readonly loading: (component: ReactNode) => ClientUrlItem;

package/dist/types/router/segment-resolution/loader-mask.d.ts

@@ -28,15 +28,15 @@ import { type RequestContext } from "../../server/request-context.js";
 export declare function isShellCaptureActive(reqCtx?: RequestContext<any> | undefined): boolean;
 export { createMaskedLoaderPromise } from "./mask-nested.js";
 /**
- * Lane decision for an entry's loaders under PPR (the loading() value decides;
- * docs/design/loader-container-bake.md):
- *
- * - RENDERABLE loading() (the LoaderBoundary Suspense fallback) — the LIVE
- *   lane: masked at capture, guaranteed fresh on every serve. Returns true.
- * - No loading() (absent, or explicitly `false`, incl. `loading(x, { ssr:
- *   false })` under the SSR manifest) — the BAKE lane: the loader executes
- *   during capture, its settled container bakes, nested pending promises hole
- *   at the consumer's own Suspense. Returns false.
+ * Entry-level lane input for an entry's loaders under PPR (the loading()
+ * value; docs/design/loader-container-bake.md). The CAPTURE decision itself
+ * is per LOADER in loader-cache.ts: a `stream: "navigation"`
+ * (awaitBeforeFlush) loader BAKES at capture regardless of this value — the
+ * flag's document promise ("data in the HTML before first flush") maps to
+ * the frozen prelude — while every other loader is LIVE (masked at capture,
+ * fresh on every serve), postponing at loading() or an inline Suspense.
+ * This helper still gates which entries pass a bake segment key for the
+ * legacy loading()-less shape and the HIT-tail seed overlay.
  *
  * Mirrors segment-system's isRenderableLoading so the mask decision and the
  * tree's boundary placement can never disagree.

package/dist/types/urls/path-helper-types.d.ts

@@ -151,7 +151,10 @@ export type PathHelpers<TEnv> = {
      * Pass `{ stream: "navigation" }` to await this loader before first flush
      * on DOCUMENT requests (see {@link LoaderOptions}) — the opt-in for loaders
      * whose data, handle pushes, or thrown notFound()/redirect() must be in the
-     * SSR'd HTML. Per-loader: a dynamic sibling keeps streaming.
+     * SSR'd HTML. Per-loader: a dynamic sibling keeps streaming. Under a
+     * `ppr` route the flag BAKES: the loader executes at shell capture and
+     * its settled return freezes into the shell (nested promises stay live
+     * holes) — the pre-flush promise applied to the prelude.
      */
     loader: <TData>(loaderDef: LoaderDefinition<TData>, optionsOrUse?: LoaderOptions | (() => LoaderUseItem[]), use?: () => LoaderUseItem[]) => LoaderItem;
     /**

package/dist/types/vite/plugins/client-ref-dedup.d.ts

@@ -4,17 +4,6 @@ import type { Plugin } from "vite";
  * Handles scoped packages (@org/name) and nested node_modules.
  * Returns null if the path doesn't contain a valid package reference.
  *
- * NOTE: This is a lossy transformation. It maps a specific submodule path
- * (e.g., pkg/internal/context.js) to the package root (pkg). The load()
- * hook then re-exports via the bare specifier, which resolves to the
- * package entry point. This works for packages that barrel-export their
- * "use client" symbols from the root, which covers the common case
- * (component libraries like @mantine/core, @chakra-ui/react, etc.).
- * Packages whose client symbols are only available from deep subpaths
- * (not re-exported from the root) would lose those symbols after the
- * rewrite. A more precise approach would resolve through the package's
- * exports map to find the correct entry point, but that adds significant
- * complexity for a rare edge case.
  * See: https://github.com/cloudflare/vinext/pull/413
  */
 export declare function extractPackageName(absolutePath: string): string | null;