Package Manager
Riot’s package manager is not a separate product bolted onto the toolchain. It is the part that turns package workflows into something repeatable and publishable.
riot addAdd dependencies and let Riot update manifests, solve versions, and refresh the lock state.riot installMaterialize runnable binaries and tools in a way that still respects Riot’s package model.riot publishTake a package from local development to a publishable artifact without hand-assembling the release flow.riot docGenerate package docs from public interfaces and keep them aligned with the package graph.
What this tab covers
Section titled “What this tab covers”- adding and removing dependencies
- updating and searching packages
- installing runnable binaries
- publishing to the registry
- generating package docs
- understanding lockfiles and caches
Two ways to read it
Section titled “Two ways to read it”- use the
Core Commandsgroup if you want operational flows - use
Advanced Topicsif you need to understand why the system behaves the way it does
The workflows that matter most
Section titled “The workflows that matter most”LockfilesUnderstand how Riot records solved dependency state and why builds stay reproducible across commands.CachesLearn how local and global caches shorten the loop without making the system feel opaque.Isolated InstallsSee how Riot can install and run tools without collapsing into global-environment chaos.Garbage CollectionUse
riot clean to reclaim old build and package state without guessing what is safe to delete.