import { FlowBuilderProps } from './types';
/**
 * FlowBuilder — Exotel Design System wrapper around React Flow.
 *
 * A thin, controlled-only presentation layer over `<ReactFlow>`:
 * - Ships NO built-in node types — `nodeTypes` is a required prop.
 * - Bakes in the Figma-verified `<Background>` / `<MiniMap>` defaults and the
 *   pan/zoom/interaction defaults CJO's `JourneyBuilderPage` already solved, so no
 *   consumer has to rediscover them (invisible dots at low zoom, a minimap that
 *   stays light in dark mode, the React Flow attribution badge, etc).
 * - Derives `colorMode` from `useFlowTheme()` (→ `useThemeMode()`) unless a
 *   consumer pins it explicitly.
 * - Provides `layoutDirection` and an optional `nodeRegistry` to descendants via
 *   `FlowDirectionContext` / `FlowNodeRegistryContext` (see `useFlowDirection` /
 *   `useFlowNodeRegistry`) — additive, so neither requires a consumer to thread
 *   props by hand.
 * - Holds no graph state of its own: `nodes`/`edges` arrive as props inherited
 *   from `ReactFlowProps`. `useFlowBuilder` remains exported as a Storybook/toy
 *   convenience hook, but it is not part of this component's contract.
 */
declare function FlowBuilderComponent({ nodeTypes, edgeTypes: edgeTypesProp, colorMode: colorModeProp, layoutDirection, interactionMode, showBackground, showMinimap, backgroundProps, minimapProps, nodeRegistry, style, className, children, ...rest }: FlowBuilderProps): import("react/jsx-runtime").JSX.Element;
export { FlowBuilderComponent as FlowBuilder };
/**
 * Alias for `FlowBuilder`. `01-canvas.md` calls the concept `FlowCanvas`
 * internally, but the published package subpath, export name, and Storybook
 * title all say `FlowBuilder` — keeping both names avoids breaking either
 * vocabulary (see `01-canvas.md` §10, "`FlowCanvas` vs `FlowBuilder` naming").
 */
export declare const FlowCanvas: typeof FlowBuilderComponent;
export type { FlowBuilderProps as FlowCanvasProps } from './types';