gemi 0.58.0 → 0.59.0

package/dist/chunks/{ThemeProvider-li1J_igh.js → ThemeProvider-ByU4BQdL.js}

@@ -2502,6 +2502,72 @@ if (typeof window !== "undefined" && process.env.NODE_ENV !== "test") {
 	const { componentTree = [] } = window.__GEMI_DATA__ ?? {};
 	for (const viewName of flattenComponentTree(componentTree)) viewImportMap[viewName] = lazy(() => loadViewModule(viewName));
 }
+/**
+* How long hydration will wait for those modules before giving up on them.
+*
+* Only a load that never *settles* reaches this — a stalled HTTP/2 stream, a
+* service worker that never answers. A rejection is already handled. Without
+* a deadline that case costs the whole document: nothing hydrates, and
+* nothing is raised. Expiring it just puts the page back on the pre-#352 path
+* for one route, which is a bad outcome and not a dead one.
+*/
+var INITIAL_VIEW_MODULES_DEADLINE_MS = 2e3;
+/**
+* Resolves once the views the document was server-rendered with are in the
+* registry — which is what `init` waits for before it hydrates.
+*
+* Hydrating before then is what made a cold load blank its own content. The
+* server renders each route segment through a real component, so the shell
+* ships complete `<Suspense>` boundaries; the browser renders the same
+* segments through `lazy()`, so on the first client render every one of them
+* suspends. React keeps the server HTML up while a boundary is merely
+* suspended, but the moment any update reaches one — the module registry
+* announcing the chunk, an effect, a settling query — it gives up on that
+* boundary and shows the fallback instead, which for a view without a
+* `Loading` export is `null`. The page then sits with its layout and no
+* content until the chunk's `import()` and dictionaries resolve.
+*
+* What this buys is NOT a synchronous `lazy()`. `lazy` suspends on its first
+* render no matter what: the initializer calls the ctor, attaches `.then`,
+* and re-reads a status its callback only sets a microtask later, so even an
+* already-settled promise goes to `Pending` and throws. The render still
+* suspends here — it just suspends *untouched*. `loadViewModule` notifies its
+* listeners only on a view's FIRST registration, so once the module is in
+* `viewModules` the call `lazy` makes during hydration is a silent one, the
+* boundary sees no update, and React keeps the server HTML until it settles.
+*
+* The invariant to preserve, then, is "no first registration for a mounted
+* view happens during hydration" — not anything about how `lazy` resolves.
+* Notifying on every call, or memoizing the promise so the `isNew` guard
+* stops being the discriminator, would reintroduce the flash while leaving
+* this preload apparently intact.
+*
+* It is not free. The view chunks themselves are already `modulepreload`ed by
+* the shell, but `loadViewModule` also awaits `preloadDictionaries`, and
+* dictionary locale chunks are dynamic imports, which `collectModulePreloads`
+* deliberately leaves out of those hints. So hydration is gated on a
+* serially-discovered round trip — view chunk, parse, dictionary chunk — and
+* the layout's own handlers stay dead across it. That wait is deliberate
+* rather than incidental: a view whose dictionary is still in flight suspends
+* on `use()` inside this same boundary, which is the same blank arriving by a
+* different route. Warming the current locale's dictionaries from the shell
+* would buy the interactivity back; awaiting less here would not.
+*
+* Never rejects and never waits forever: a chunk that fails or hangs must
+* still leave the app to hydrate and surface the error through the route's
+* error boundary.
+*/
+var initialViewModulesReady = typeof window !== "undefined" && process.env.NODE_ENV !== "test" ? Promise.race([Promise.all(initialViewNames(window.__GEMI_DATA__).map((name) => loadViewModule(name).catch(() => null))), new Promise((resolve) => setTimeout(resolve, INITIAL_VIEW_MODULES_DEADLINE_MS))]) : Promise.resolve();
+/**
+* The view names the server rendered this document with — the same lookup
+* `ClientRouterProvider` seeds its route state from, so the two agree on what
+* the first render is going to mount.
+*/
+function initialViewNames(data) {
+	if (!data?.router) return [];
+	if (data.router.is404) return ["404"];
+	return data.routeManifest?.[data.router.pathname] ?? ["404"];
+}
 var ComponentsContext = createContext({
 	viewImportMap,
 	getViewModule
@@ -2920,6 +2986,6 @@ function useTheme() {
 	return context;
 }
 //#endregion
-export { createMemoryHistory as A, QueryError as B, I18nContext as C, useLocation as D, ServerDataProvider as E, applyParams as F, QueryConfigContext as I, QueryManagerContext as L, RouteStateContext as M, RouteStateProvider as N, ProgressManager as O, toVariantKey as P, QueryManagerProvider as R, useNavigate as S, ServerDataContext as T, Subject as V, setActiveLocale as _, m as a, useRoute as b, ClientRouterContext as c, ComponentsProvider as d, loadViewModule as f, registerDictionary as g, loadDictionaryForRender as h, WebSocketContextProvider as i, useParams as j, Action as k, ClientRouterProvider as l, loadDictionary as m, useTheme as n, RouteTransitionProvider as o, subscribeViewModules as p, WebSocketContext as r, useRouteTransition as s, ThemeProvider as t, ComponentsContext as u, readRoutePayload as v, I18nProvider as w, useSearchParams as x, routeDataUrl as y, DEFAULT_STALE_TIME as z };
+export { Action as A, DEFAULT_STALE_TIME as B, useNavigate as C, ServerDataProvider as D, ServerDataContext as E, toVariantKey as F, Subject as H, applyParams as I, QueryConfigContext as L, useParams as M, RouteStateContext as N, useLocation as O, RouteStateProvider as P, QueryManagerContext as R, useSearchParams as S, I18nProvider as T, QueryError as V, registerDictionary as _, m as a, routeDataUrl as b, ClientRouterContext as c, ComponentsProvider as d, initialViewModulesReady as f, loadDictionaryForRender as g, loadDictionary as h, WebSocketContextProvider as i, createMemoryHistory as j, ProgressManager as k, ClientRouterProvider as l, subscribeViewModules as m, useTheme as n, RouteTransitionProvider as o, loadViewModule as p, WebSocketContext as r, useRouteTransition as s, ThemeProvider as t, ComponentsContext as u, setActiveLocale as v, I18nContext as w, useRoute as x, readRoutePayload as y, QueryManagerProvider as z };
 
-//# sourceMappingURL=ThemeProvider-li1J_igh.js.map
+//# sourceMappingURL=ThemeProvider-ByU4BQdL.js.map