import { type Plugin } from 'vite';
import type { OptionsContext } from './context.js';
/** Where Chrome DevTools looks for a workspace folder to connect. */
export declare const DEVTOOLS_JSON_PATH = "/.well-known/appspecific/com.chrome.devtools.json";
/**
 * A v4-shaped UUID hashed from `root`, so DevTools recognises the same
 * workspace across server restarts instead of offering a new one each time.
 */
export declare const workspaceUuid: (root: string) => string;
/**
 * Answers `root` and its UUID on {@link DEVTOOLS_JSON_PATH}. The reply names
 * an absolute path on this machine, so only loopback clients get it; a dev
 * server exposed with `--host` passes everyone else on.
 */
export declare const createDevtoolsJsonMiddleware: (root: string) => (req: {
    url?: string;
    socket?: {
        remoteAddress?: string;
    };
}, res: {
    setHeader(name: string, value: string): void;
    end(body: string): void;
}, next: () => void) => void;
/**
 * Lets Chrome DevTools connect the project as a workspace, so edits made in
 * the Sources panel save to disk. The root defaults to Vite's workspace root
 * (the monorepo root, not the app), since sources served from sibling
 * packages would otherwise fall outside it and stay unmapped.
 */
export declare const litDevtoolsWorkspace: (ctx: OptionsContext) => Plugin;
//# sourceMappingURL=devtools-workspace.d.ts.map