If your team standardizes on pnpm, yarn, or bun, you can install the Vibgrate CLI (@vibgrate/cli) with any of them. The installed binary is always vg, and a bare vg scans the current directory.
pnpm
Global install:
pnpm add -g @vibgrate/cli
Project dev dependency:
pnpm add -D @vibgrate/cli
Run it:
vg
yarn
Global install:
yarn global add @vibgrate/cli
Project dev dependency:
yarn add --dev @vibgrate/cli
bun
Global install:
bun add -g @vibgrate/cli
Project dev dependency:
bun add -d @vibgrate/cli
Verify and scan
After any of the above:
vg --version
vg
Vibgrate reports a DriftScore from 0 to 100 and the findings it detected.
Run without a global install
Each package manager can execute the CLI directly:
pnpm dlx @vibgrate/cli scan
yarn dlx @vibgrate/cli scan
bunx @vibgrate/cli scan
These are equivalent to the npm form npx @vibgrate/cli scan.
Troubleshooting
vg: command not foundafter a global install — confirm your package manager's global bin directory is on PATH. pnpm in particular requires running its setup step once.- Version drift across the team — prefer a project dev dependency so everyone runs the same CLI version.
Related
See install the Vibgrate CLI with npm for the npm-specific path, or learn how to run Vibgrate with npx and no install.