pinset install
Install tools from the project lock so a new computer or CI can restore the agreed toolchain.
View source on GitHub ↗When to use
Use after cloning, to add missing installations or repair damaged ones. Change versions with use.
Examples
pinset install
pinset install node pnpm --offline
Result: the first installs locked tools and bindings. The second restores only Node, pnpm and their locked dependencies from local cache; missing cache fails.
Behavior
Configuration and lock must be valid and match. Uses locked versions, URLs and digests, verifying downloads and cache without resolving versions. Writes installations, command entries and local bindings, including managed Python environments or Flutter links when required. Choices remain unchanged. Named installation handles only those tools and runtime dependencies, leaving unrelated environments/links alone.
--repair does not take over external installations. --recreate-venv requires a valid managed environment and a selected set including Python. Interactive stderr shows stages, progress and cache reuse for use and install; known sizes include percentage, speed and time remaining. JSON or redirected stderr hides progress UI.
Parameters, exit codes and common errors
| Parameter | Meaning |
|---|---|
[tool...] | Named tools and dependencies; omit for all project tools. |
--global | Use the global lock. |
--offline | Use valid installs or verified cache without downloading. |
--repair | Repair managed installations. |
--recreate-venv | Explicitly rebuild managed project Python. |
--plan | Plan only, without downloads or writes. |
Success exits 0; failure exits 1. PINSET_LOCK_MISSING needs a maintainer-generated lock; PINSET_LOCK_MISMATCH needs choices aligned through use; PINSET_TOOL_NOT_SELECTED names an unselected tool. External .venv directories are preserved; inspect ownership first.