import { toast, RobotToastOptions } from 'robot-toast';
export { RobotToastAPI, RobotToastOptions, ToastPosition, ToastTheme, ToastType, TransitionType, toast } from 'robot-toast';

/**
 * robot-toast — React bindings
 * ─────────────────────────────────────────────────────────────────────────────
 * Thin React wrapper around the framework-agnostic core. The toast manager is
 * already a module-level singleton, so there's no Provider / Context needed —
 * just a hook that hands you the `toast` function with a stable reference.
 *
 *   import { useRobotToast } from 'robot-toast/react';
 *
 *   function SaveButton() {
 *     const toast = useRobotToast();
 *     return <button onClick={() => toast.success('Saved!')}>Save</button>;
 *   }
 *
 * For mount-scoped toasts (fire on mount, auto-close on unmount), use
 * `useToastOnMount`. Typical case: surfacing a persistent loading/status toast
 * while a component is on screen.
 */

/**
 * Returns the `toast` function. Stable across re-renders.
 * Equivalent to `import { toast } from 'robot-toast'`, but follows the
 * idiomatic React hook shape some teams prefer.
 */
declare function useRobotToast(): typeof toast;
/**
 * Fire a toast when the component mounts, close it when the component unmounts.
 * `options` is read once (on mount) — subsequent changes do not update the toast.
 * To show a new toast, remount the component (e.g. via `key`).
 */
declare function useToastOnMount(options: RobotToastOptions): void;

export { useRobotToast, useToastOnMount };