← Back to the index

vv vendor

Copies all dependencies into a local .vv-modules directory. This is useful for ensuring reproducible builds without relying on external network access.

vv vendor

Project Integrity with vv.mod

When you run vv vendor without arguments, it perform the following actions:

  1. Dependency Discovery: Recursively scans all .vv files in your project to find every imported remote module.
  2. Local Copying: Copies these modules from your global $VVPATH/.cache into the project's .vv-modules directory.
  3. Locking: Creates (or updates) a vv.mod file at your project root.

The vv.mod file acts as a lock file. It contains cryptographic checksums for every file in the .vv-modules directory, ensuring that your dependencies haven't been tampered with or accidentally modified.