import { ReactNode } from '../../../../node_modules/react';
import { NodeHoverToolbarProps } from './NodeHoverToolbar';
interface NodeWithHoverToolbarProps extends NodeHoverToolbarProps {
    children: ReactNode;
    selected?: boolean;
    showToolbar?: boolean;
}
/**
 * Wraps a node/note with a floating hover-action toolbar, using `useHoverToolbar()` +
 * `<HoverBridge />` as ordinary absolutely-positioned siblings rather than React Flow's own
 * `<NodeToolbar>` — `<NodeToolbar>` portals its content into a shared
 * `.react-flow__renderer` container outside this component's own DOM subtree
 * (`NodeToolbarPortal` → `createPortal`), so a bridge element placed "inside" it cannot sit,
 * as a DOM descendant, between this wrapper and the card the way a bridge must to keep hover
 * state from dropping. Rendering the toolbar as a plain sibling — CJO's actual approach in
 * `JourneyBuilderPage.tsx` — keeps the bridge, the toolbar, and the card in one DOM subtree so
 * hover state never drops while the pointer crosses the gap.
 */
declare function NodeWithHoverToolbarComponent({ children, selected, showToolbar, ...toolbarProps }: NodeWithHoverToolbarProps): import("react/jsx-runtime").JSX.Element;
export declare const NodeWithHoverToolbar: import('../../../../node_modules/react').MemoExoticComponent<typeof NodeWithHoverToolbarComponent>;
export {};