export interface InstallVerifyResult { ok: boolean; /** Missing modules, with the resolution error. Empty when `ok`. */ missing: { module: string; error: string; }[]; /** Set when the check could not run at all (never treat as "fine"). */ checkError?: string; } /** * Verify the CURRENT install resolves everything the daemon needs. * * Runs in a child `node -e` so a throw cannot take the caller down, and so the * resolution happens in a fresh module registry rather than this process's * already-warm one (which would happily report success for a module it loaded * before the install clobbered it). */ export declare function verifyInstall(): InstallVerifyResult; /** One-line human summary for the upgrade log and the diagnostic. */ export declare function describeVerify(result: InstallVerifyResult): string; /** * npm's in-flight backup directories, newest first. * * When a global install aborts, npm leaves the previous tree at * `node_modules/.-XXXXXX`. It is the only complete copy of a working install * on the machine, so the rollback path reads it from here. `package.json` is * frequently missing from it (npm removed it during the rename), which is why * callers must restore `node_modules` rather than the whole directory. */ export declare function npmBackupDirs(): string[];