import type { Plugin } from 'vite';
import type { MurasakiConfig } from '../config.js';
interface Options {
    config: MurasakiConfig;
}
/**
 * Dev-time counterpart of the updater's HTTP contract
 * (`runtime/updater.ts`'s `createUpdateRequestHandler`, contract §6) — mounts
 * `/__murasaki/update/*` the same way `server-actions.ts`/`api-routes.ts`
 * mount theirs. `check` works in dev (so a manifest/key pair can be
 * validated without a full `murasaki bundle`); `download`/`install` fail
 * fast with the contract's fixed error string — there's no bundled app or
 * launcher binary to apply an update to yet.
 *
 * `resolveUpdater()` runs once at dev-server start (not per request), same
 * timing as `cli/bundle.ts`'s `metaJson()` — a broken `updater` config (e.g.
 * `repo` + `endpoint` both set) fails the same way in both: here it fails
 * `murasaki dev` startup, there it fails `murasaki bundle`. Never a silent
 * runtime no-op.
 */
export declare function updaterPlugin({ config }: Options): Plugin;
export {};
//# sourceMappingURL=updater.d.ts.map