/**
 * Web variant of the Portal API.
 *
 * On native we keep the context-based portal group (the consumer mounts a
 * `<Provider />` near the root and an `<Outlet />` to render portaled
 * components inside the native view hierarchy). On web there's a stable
 * `document.body`, so we portal directly there via `react-dom`'s native
 * `createPortal` — no provider, no outlet, no setup. This matches how
 * mature web component libraries (Radix, Mantine, Tamagui) ship their
 * portals.
 *
 * The native and web APIs are kept identical: `Provider` and `Outlet` are
 * still exported on web — they just become harmless no-op fragments so
 * consumers that *do* mount them keep compiling.
 */
import React from 'react';
export declare function Portal({ children }: React.PropsWithChildren<object>): React.ReactPortal | null;
export declare function Provider(props: React.PropsWithChildren<object>): import("react/jsx-runtime").JSX.Element;
export declare const Outlet: React.NamedExoticComponent<object>;
//# sourceMappingURL=index.web.d.ts.map