import React from "react";
/**
 * Does this error mean a chunk could not be loaded — rather than the chunk's
 * own code throwing once it did load?
 *
 * Errors raised anywhere are matched, not just ones `loadChunk` produced: React
 * `lazy()` calls that still import directly, and Vite's own CSS preloads, fail
 * the same way and deserve the same recovery.
 */
export declare function isChunkLoadError(error: unknown): boolean;
/**
 * Run a dynamic import, retrying once before declaring the chunk unreachable.
 *
 * Errors that are not chunk load failures — the imported module throwing while
 * it evaluates, say — are re-thrown untouched and never retried: running a
 * module's side effects twice is worse than the original failure.
 */
export declare function loadChunk<T>(loader: () => Promise<T>): Promise<T>;
/**
 * `React.lazy` with the retry above. A drop-in replacement — use it for every
 * lazy route or dialog, since any one of them can be the first chunk a stale
 * tab reaches for.
 *
 * Note that React caches the rejection: once a lazy component has failed, later
 * renders re-throw without calling the loader again. Resetting an error boundary
 * therefore cannot recover it, which is why the boundary offers a reload.
 */
export declare function lazyChunk<T extends React.ComponentType<any>>(loader: () => Promise<{
    default: T;
}>): React.LazyExoticComponent<T>;