/**
 * `chkit init` scaffolds a `clickhouse.config.ts` that imports `@chkit/core` (and
 * `@chkit/plugin-obsessiondb` once onboarding registers it), but the docs `init` flow assumes the
 * user already ran `bun add -d chkit`. In a brand-new empty directory nothing is installed, so the
 * scaffold looks complete but the first `generate` dead-ends on unresolved imports. This module
 * detects that case and installs the packages so the project is runnable.
 */
export type PackageManager = 'npm' | 'pnpm' | 'yarn' | 'bun';
/**
 * Whether `@chkit/core` resolves from the *project* directory. Resolving against `cwd` (not the
 * CLI's own location) is the point: it tells us if the user's project can load its scaffolded
 * config, regardless of where the running `chkit` binary lives.
 */
export declare function projectHasCoreDependency(cwd: string): boolean;
/** Detect the package manager from `npm_config_user_agent`; default to bun (this repo is bun-first). */
export declare function detectPackageManager(env?: NodeJS.ProcessEnv): PackageManager;
/** Build the dev-dependency install command for a package manager. */
export declare function installCommand(pm: PackageManager): {
    cmd: string;
    args: string[];
};
/**
 * Make the project runnable by installing chkit + its plugins when they're missing.
 * Returns true if an install was run, false if deps were already present or the install failed
 * (a failed install never throws — init keeps going and prints the manual command instead).
 */
export declare function ensureProjectDependencies(cwd: string, print: (msg: string) => void): Promise<boolean>;
//# sourceMappingURL=deps.d.ts.map