@plasmicapp/loader-react 1.0.253 → 1.0.254

package/dist-react-server/loader-react-server.d.ts

@@ -1,72 +0,0 @@
-import { LoaderBundleCache, PageMeta, PlasmicModulesFetcher, PlasmicTracker } from '@plasmicapp/loader-core';
-import { ComponentMeta, LoaderBundleOutput } from '@plasmicapp/loader-fetcher';
-import { ComponentRenderData, FetchPagesOpts } from './loader';
-import { ComponentLookupSpec } from './utils';
-export interface InitOptions {
-    projects: {
-        id: string;
-        token: string;
-        version?: string;
-    }[];
-    cache?: LoaderBundleCache;
-    platform?: 'react' | 'nextjs' | 'gatsby';
-    preview?: boolean;
-    host?: string;
-    onClientSideFetch?: 'warn' | 'error';
-    i18nKeyScheme?: 'content' | 'hash';
-    /**
-     * By default, fetchComponentData() and fetchPages() calls cached in memory
-     * with the PlasmicComponentLoader instance.  If alwaysFresh is true, then
-     * data is always freshly fetched over the network.
-     */
-    alwaysFresh?: boolean;
-}
-/** Subset of loader functionality that works on React Server Components. */
-export declare class ReactServerPlasmicComponentLoader {
-    private readonly opts;
-    private readonly fetcher;
-    private readonly tracker;
-    private readonly onBundleMerged?;
-    private readonly onBundleFetched?;
-    private bundle;
-    constructor(args: {
-        opts: InitOptions;
-        fetcher: PlasmicModulesFetcher;
-        tracker: PlasmicTracker;
-        /** Called after `mergeBundle` (including `fetch` calls). */
-        onBundleMerged?: () => void;
-        /** Called after any `fetch` calls. */
-        onBundleFetched?: () => void;
-    });
-    private maybeGetCompMetas;
-    maybeFetchComponentData(specs: ComponentLookupSpec[], opts?: FetchComponentDataOpts): Promise<ComponentRenderData | null>;
-    maybeFetchComponentData(...specs: ComponentLookupSpec[]): Promise<ComponentRenderData | null>;
-    fetchComponentData(specs: ComponentLookupSpec[], opts?: FetchComponentDataOpts): Promise<ComponentRenderData>;
-    fetchComponentData(...specs: ComponentLookupSpec[]): Promise<ComponentRenderData>;
-    fetchPages(opts?: FetchPagesOpts): Promise<PageMeta[]>;
-    fetchComponents(): Promise<ComponentMeta[]>;
-    getActiveSplits(): import("@plasmicapp/loader-core").Split[];
-    private fetchMissingData;
-    private maybeReportClientSideFetch;
-    private fetchAllData;
-    mergeBundle(bundle: LoaderBundleOutput): void;
-    getBundle(): LoaderBundleOutput;
-    clearCache(): void;
-}
-export interface FetchComponentDataOpts {
-    /**
-     * Will fetch either code targeting SSR or browser hydration in the
-     * returned bundle.
-     *
-     * By default, the target is browser. That's okay, because even when
-     * doing SSR, as long as you are using the same instance of PlasmicLoader
-     * that was used to fetch component data, it will still know how to get at
-     * the server code.
-     *
-     * But, if you are building your own SSR solution, where fetching and rendering
-     * are using different instances of PlasmicLoader, then you'll want to make
-     * sure that when you fetch, you are fetching the right one to be used in the
-     * right environment for either SSR or browser hydration.
-     */
-    target?: 'server' | 'browser';
-}