/**
 * Live datasource state for components rendered by a Puck plugin.
 *
 * Puck receives its plugin array once per mount — useP1Editor keeps that array
 * identity-stable on purpose, since new plugin objects mean new override
 * component identities, which remounts the canvas and every field. So anything
 * a plugin factory closes over is frozen at creation time, which for datasource
 * data means permanently: the plugins are built the moment the registry first
 * exists, while the context fetch is still in flight.
 *
 * Reading through this hook instead subscribes the component to the same
 * react-query entries the editor host uses, so data, loading state, and the
 * current document path stay live without anything crossing the plugin
 * boundary.
 *
 * This also resolves every registry entry's datasource context in one request
 * — only use it where that's actually needed. A component instantiated
 * once per field should use useLiveEditorContext instead, which skips that.
 *
 * `fallbackPath` is only used outside a P1PuckProvider (e.g. the published
 * `EditorClient`), where there is no context to read the open document from.
 */
export declare function useLiveRemoteDatasources(fallbackPath: string): {
    context: import("../../../server").RemoteDatasourceContext;
    loadingIds: Set<string>;
    isLoading: boolean;
    path: string;
    branchId: string | undefined;
    hasLoaded: boolean;
    registry: import("../../..").RemoteDatasourceDefinition[];
    routes: import("../../..").RouteRow[];
    routeTemplateKeys: string[];
    savedPreviewParams: Record<string, string>;
};