vercel-projects manages multiple Vercel project configurations in one Git repository. It provides the vp command for saving named Vercel project configurations, listing them, and running Vercel commands against a selected configuration.

Install the published CLI with npm:

npm install --global vercel-projects

The npm package downloads the matching native binary from the GitHub release for macOS arm64/x64 and Linux arm64/x64. Windows is not currently supported by the prebuilt release workflow.

To build from source, install Rust and run:

cargo install --path crates/vp-cli

The vp commands must be run inside a Git repository with the Vercel CLI available on PATH.

First link the current directory with Vercel, then save its project configuration under a name:

vercel link
vp add
vp list
vp storefront build
vp storefront deploy --prod

vp add reads .vercel/project.json and stores a copy at .vercel-projects/<name>/project.json. Running vp <name> <command> [args...] switches the active .vercel/project.json when needed, runs vercel <command> [args...], and leaves the selected configuration active.

The stored files contain Vercel project and organization identifiers, not Vercel authentication credentials. Keep your Vercel CLI credentials in the normal Vercel configuration outside this repository.

cargo test --locked
cargo fmt --all -- --check
cargo clippy --locked --all-targets --all-features -- -D warnings
bun run build

Pushing a v* tag runs the GitHub Actions release workflow, which builds the platform binaries, creates a GitHub release, and publishes the npm package.

MIT. See LICENSE.