import type { Plugin } from 'vitest/config';
export interface PipeworkVitestOptions {
    globals?: boolean;
    isolate?: boolean;
    /** Set to `false` to skip auto-setup (manifold discovery, DB provisioning, per-test isolation). Use this for pure unit test configs that never call `pipe()` or `withFlow()`. */
    database?: boolean;
    /**
     * Absolute path to the project (package) root. When set, any module that
     * Vite would resolve to `<root>/dist/*.js` is rewritten to its `<root>/src/*.ts`
     * (or `.tsx`) source so `vi.mock` matches the file handlers actually import
     * — without this, a built workspace package gets split into two module
     * identities (dist + src), and mock interception silently fails. Issue #274.
     */
    packageRoot?: string;
    /**
     * Map of bare cross-package workspace specifier → absolute source file.
     * vitest does not honour tsconfig `paths`, so an import of `@scope/pkg` (or
     * one of its export subpaths) resolves through the package's `exports` field
     * to `dist/`, which is not built during `pipework test`. This routes those
     * specifiers to `src/` instead. Issue #301.
     *
     * A wildcard export subpath contributes a single `*` entry — key and value
     * both contain one `*` (e.g. `@scope/pkg/events/*` → `<abs>/pkg/src/events/*.ts`).
     * The resolver substitutes the matched segment into the value. Issue #311.
     */
    workspacePackages?: Record<string, string>;
}
export declare function pipework(options?: PipeworkVitestOptions): Plugin;
//# sourceMappingURL=vitest-plugin.d.ts.map