@weaverse/next 0.1.0-alpha.13 → 0.1.0-alpha.14

package/dist/server.d.ts

@@ -1,100 +0,0 @@
-import { x as WeaverseNextRequestContext, e as WeaverseNextBaseConfigs, C as WeaverseNextServerClient, k as WeaverseNextComponentData, D as WeaverseNextServerClientConfig } from './seo-CrEFl_Up.js';
-export { f as WeaverseNextCacheConfig, n as WeaverseNextConfigs, o as WeaverseNextCustomPageEntry, p as WeaverseNextFetchCustomPagesOptions, q as WeaverseNextFetchOptions, w as WeaverseNextProjectId, B as WeaverseNextSeoMetadata, E as WeaverseNextServerLoadPageInput, H as WeaverseNextThemeSettingsOptions, I as WeaverseNextThemeSettingsResponse, Q as formatWeaverseNextSeoMetadata, R as getWeaverseNextSeoMetadata } from './seo-CrEFl_Up.js';
-import '@weaverse/schema';
-import 'next';
-import '@weaverse/react';
-import 'react';
-
-interface ResolveConfigsOptions {
-    env?: Record<string, string | undefined>;
-    weaverseApiBase?: string;
-    weaverseHost?: string;
-    weaverseVersion?: string;
-}
-/**
- * Derive Weaverse configs from the request context and env, close to Hydrogen's
- * `getWeaverseConfigs`. Resolves the trusted host, public API base, design /
- * preview / revision flags, and public env — but never resolves the final
- * `projectId` (that priority chain, which may call an async resolver, lives in
- * the server client). Query/env projectId candidates are returned for the
- * client to combine with function/string inputs.
- */
-declare function getWeaverseNextConfigs(context?: WeaverseNextRequestContext, options?: ResolveConfigsOptions): WeaverseNextBaseConfigs;
-
-/**
- * Normalize the storefront URL sent in the Builder page API request body.
- *
- * The Builder reads only the pathname (locale/type/handle fallback) and the
- * Weaverse/Studio control params from this URL, so keep exactly those and drop
- * tracking params. Params are sorted for a stable, cache-friendly string.
- *
- * Ported from `@weaverse/hydrogen`'s `normalizePageUrl`, but tolerant of a
- * relative URL (Next route handlers may only know the pathname).
- */
-declare function normalizeNextPageUrl(url: string): string;
-/**
- * Build an absolute-ish request URL string from the explicit request context,
- * preferring `url`, then `pathname` + `searchParams`. Used as the input to
- * {@link normalizeNextPageUrl}.
- */
-declare function resolveRequestUrl(context?: WeaverseNextRequestContext): string;
-
-interface WeaverseNextRevalidateHandlerConfig {
-    /**
-     * Reuse the app's server-client factory so the loader runs with the same
-     * component registry and commerce (storefront) context as page loads.
-     */
-    getClient: (request: Request) => Promise<WeaverseNextServerClient> | WeaverseNextServerClient;
-}
-/** POST body accepted by the revalidate route. */
-interface WeaverseNextRevalidateRequestBody {
-    draftItem: WeaverseNextComponentData;
-}
-/**
- * Create the Studio per-item revalidation route handler.
- *
- * Studio design-mode edits to loader-backed inputs (e.g. resource pickers) need
- * fresh server loader data for a single item. Re-running it through
- * `router.refresh()` re-applies the whole RSC tree — and the draft-item query
- * rewrite changes the App Router page segment key, remounting the page and
- * resetting scroll. This handler runs just the edited component's `loader`
- * with the unsaved draft settings and returns the payload for an in-place
- * client update (see the `2026-07-02--next-item-revalidation` spec).
- *
- * Security: only registered component types are executable, the handler never
- * persists anything, and responses are `no-store`. Exposure is equivalent to
- * the existing `weaverseDraftItem` URL param, which already lets any visitor
- * run design-mode loaders with arbitrary draft settings.
- *
- * @example
- * ```ts
- * // app/api/weaverse/revalidate/route.ts
- * export const { POST } = createWeaverseNextRevalidateHandler({
- *   getClient: () => getWeaverseServerClient(Promise.resolve({})),
- * })
- * ```
- */
-declare function createWeaverseNextRevalidateHandler(config: WeaverseNextRevalidateHandlerConfig): {
-    POST: (request: Request) => Promise<Response>;
-};
-
-/**
- * Create a server-side {@link WeaverseNextServerClient} for Next.js App Router
- * routes / server components.
- *
- * @example
- * ```ts
- * let weaverse = createWeaverseNextServerClient({
- *   projectId: process.env.WEAVERSE_PROJECT_ID,
- *   components,
- *   commerce: { storefront },
- *   requestContext: { url, headers, searchParams, i18n },
- *   cache: { revalidate: 60, tags: ['weaverse'] },
- * })
- * let data = await weaverse.loadPage({ type: 'INDEX' })
- * let theme = await weaverse.loadThemeSettings()
- * ```
- */
-declare function createWeaverseNextServerClient(config: WeaverseNextServerClientConfig): WeaverseNextServerClient;
-
-export { WeaverseNextBaseConfigs, type WeaverseNextRevalidateHandlerConfig, type WeaverseNextRevalidateRequestBody, WeaverseNextServerClient, WeaverseNextServerClientConfig, createWeaverseNextRevalidateHandler, createWeaverseNextServerClient, getWeaverseNextConfigs, normalizeNextPageUrl, resolveRequestUrl };