import type { Alias } from "vite";
/**
 * Vite alias mapping the React 19-only `react/compiler-runtime` specifier to
 * the React-team `react-compiler-runtime` shim, which is API-compatible on
 * React 17/18. Shared by the live-edit dev server and the production build so
 * that user code (or a dependency) emitting `react/compiler-runtime` imports
 * resolves against our React 18.3.1 runtime instead of crashing Vite
 * resolution with `Missing "./compiler-runtime" specifier in "react" package`
 * (APPS-2887).
 *
 * The exact-match string `find` fires only for `react/compiler-runtime`, never
 * `react`, `react/jsx-runtime`, or `react-dom`.
 *
 * Returns `null` (and logs) if the shim package cannot be resolved — e.g. a
 * corrupted or partial SDK install. Skipping the alias keeps the dev server /
 * build starting for every other app instead of throwing synchronously inside
 * `createServer()`/`build()` and permanently rejecting `vitePromise`, which
 * would reproduce the very infinite-spinner symptom this fix removes. Only an
 * app that actually imports `react/compiler-runtime` would then hit the
 * original (now clearly-logged) resolution error.
 */
export declare function reactCompilerRuntimeAlias(resolve?: (id: string) => string): Alias | null;
//# sourceMappingURL=react-compiler-runtime-shim.d.mts.map