/**
 * Types for the `@lotics/ui/vite` subpath (runtime lives in `vite.mjs`).
 *
 * The Vite `resolve` block for a Lotics custom-code app. Reads `LOTICS_UI_SRC`
 * at call time, so the dev-link is decided per command.
 */
export declare function loticsResolve(): {
  alias: { find: RegExp; replacement: string }[];
  dedupe: string[];
};

/**
 * The directories outside the app a dev server must also serve from — the
 * dev-linked kit, else nothing. ADDITIONS: spread into a `server.fs.allow` that
 * still names the app's own workspace root, which setting the key replaces.
 */
export declare function loticsFsAllow(): string[];

/**
 * The `optimizeDeps` block: every published kit subpath, so none of them is a
 * dependency Vite meets for the first time mid-session — which re-optimizes,
 * reloads, and under `lotics app dev`'s sandboxed iframe leaves two Reacts
 * ("Invalid hook call") until a cold restart. Empty under `LOTICS_UI_SRC`, where
 * the kit is source rather than a dependency.
 */
export declare function loticsOptimizeDeps(): { include: string[] };