import type { Package } from "../../utils/packageJson.js";
/**
 * One-shot Vercel CLI binding for a single workspace package. The constructor
 * resolves the package's `VERCEL_PROJECT_ID_<NAME>` env var and throws
 * `MissingVercelProjectIdError` if it's not set — so successful construction
 * is itself the "this package is deployable" check used by the deploy
 * command's filter.
 *
 * `VERCEL_TOKEN` and `VERCEL_ORG_ID` are read lazily inside `pull()` and
 * `deploy()` so dry-runs (which never invoke them) succeed even when those
 * env vars are absent.
 *
 *     const vercel = new Vercel(pkg);
 *     await vercel.pull("preview");
 *     await vercel.build();
 *     const url = await vercel.deploy("preview");
 *
 * See https://vercel.com/docs/cli
 */
export declare class Vercel {
    #private;
    readonly pkg: Package;
    constructor(pkg: Package);
    /**
     * `vercel pull --cwd <pkg.location> --environment <env> --yes`. Reads
     * `VERCEL_TOKEN` and `VERCEL_ORG_ID` at call time.
     *
     * @see https://vercel.com/docs/cli/pull
     */
    pull(environment: string): Promise<void>;
    /**
     * Produces the Build Output API artifact at
     * `<pkg.location>/.vercel/output/`. Pure filesystem — no `vercel` CLI
     * invocation, no Vercel credentials required.
     */
    build(vercelConfigOverride?: string): Promise<void>;
    /**
     * `vercel deploy <pkg.location> --prebuilt --target <target>`, returning
     * the deployment URL printed on stdout's last non-empty line. When
     * `target` is `"production"`, uses `--prod --skip-domain` instead of
     * `--target=production`, matching Vercel CLI conventions. Reads
     * `VERCEL_TOKEN` and `VERCEL_ORG_ID` at call time.
     *
     * @see https://vercel.com/docs/cli/deploy
     */
    deploy(target: string): Promise<string>;
}
//# sourceMappingURL=vercel.d.ts.map