vlt / docs

  • PricingBenchmarks (opens in new window)Community (opens in new window)Feedback
  • Overview
  • bugs
  • build
  • cache
  • ci
  • config
  • create
  • deploy
  • docs
  • exec-cache
  • exec-local
  • exec
  • help
  • init
  • install
  • list
  • login
  • logout
  • outdated
  • pack
  • ping
  • pkg
  • publish
  • query
  • registry
  • repo
  • run-exec
  • run
  • setup
  • skills
  • token
  • uninstall
  • update
  • version
  • view
  • whoami
  • Lifecycle scripts
  • Workspaces
  • Options
  1. Client
  2. /
  3. Commands
  4. /
  5. ci

vlt ci

Usage:

Terminal
$ vlt ci

Clean install for CI pipelines. Removes node_modules and installs dependencies exactly as specified in vlt-lock.json, failing if the lockfile is missing or out of date.

Lifecycle scripts

Like vlt install, vlt ci runs no lifecycle scripts of dependencies by default. To opt in:

Terminal
# Allow scripts for specific packages, this run only
$ vlt ci --allow-scripts="#esbuild"

# Save the query as allow-scripts in vlt.json: vlt ci runs it

$ vlt build "#esbuild"

# Or build after install: the stored query, else the default (no TTY: not saved)

$ vlt ci && vlt build

See vlt build for allow-scripts.

Workspaces

vlt ci reads workspaces from vlt.json only. If they are declared only in package.json or pnpm-workspace.yaml, it warns and ignores them: run vlt install and commit vlt.json (see Workspaces).

Options

FlagDescription
--allow-scripts=<query>Allow matching packages to run lifecycle scripts (never saved)
--allow-skills=<query>Link the agent skills of matching packages (never saved), see vlt skills
--skills-dir=<path>Dirs to link agent skills into, see vlt skills

PreviouscacheNextconfig

On this page

  • Lifecycle scripts
  • Workspaces
  • Options
Edit this page

Deploy your package on vlt.io

Publish scoped and private packages, manage organizations and access, and give every developer and CI environment a consistent source for public and private JavaScript dependencies.

Publish now