sauce runtime reports where the MCP server and Solana simulations load their dependencies. Use it to inspect or install those runtime packages.
Synopsis
Description
Two commands load packages that an install of@eco-incorp/sauce leaves out, because they are its optional peer dependencies:
Each command uses your own copies where the package resolves them at exactly the versions it pins. Otherwise it uses this version’s runtime folder,
~/.sauce/runtime/<version>. The first command that needs the folder installs it and says so on stderr.
The install runs npm ci on the lockfile the package ships, so every package is the pinned one, checked against its integrity hash. npm runs with no install scripts, in a temporary directory that is renamed into place only when npm succeeds, so a failed install leaves nothing half-installed. The folder is created owner-only, and the command refuses to install into it or load from it when another user owns it or can write a folder above it. npm reaches the registry your npm configuration names, a mirror or proxy included. After an install, the folders of older versions are removed, except the newest of them.
sauce mcp setup and sauce update install the folder before its first use. sauce mcp --offline installs nothing.
Options
Output
status prints the folder, whether it is installed, and for each command its packages and their source: your own copies, the runtime folder, or not installed yet (the first use installs them). A copy of your own at another version than the pinned one is named, with a note that it is not used. install prints the packages and the folder it installed them in. With --json, status prints: