import { type WebpackGlobalsOptions } from "./installWebpackGlobals.js";
export type CreateWebpackClientOptions = WebpackGlobalsOptions;
/**
 * Installs the webpack module-loading globals, then loads the vendored
 * webpack flight client. Returns the client module namespace
 * (`createFromReadableStream`, `createFromFetch`, `createServerReference`,
 * `encodeReply`, …).
 *
 * WHICH client build loads is decided by the ENVIRONMENT, not an option: the
 * `react-server-loader/webpack/client` export maps resolve conditions to the
 * right vendored build (browser default, `node`, and the `workerd` / `deno` /
 * `edge-light` edge family). The previous `target` option enumerated literal
 * imports of every variant, which made bundlers ship all three — a browser
 * bundle carried the Node build (and its `node:util` import) as dead weight.
 * A host that genuinely needs a specific variant imports it explicitly
 * (`react-server-loader/webpack/client.edge`) and calls
 * `installWebpackGlobals` itself.
 */
export declare function createWebpackClient(options?: CreateWebpackClientOptions): Promise<Record<string, unknown>>;
//# sourceMappingURL=createWebpackClient.d.ts.map