Choose the project root
Placejolter.json at the highest directory that should share one runtime and tool set.
jolter.json files only when a subtree intentionally needs a different toolchain.
Pin the runtime
From the project root:Pin tools
Built-in tools run through Node.js, so they require a Node.js runtime.jolter.json
Synchronize the project
sync resolves the project, installs or reuses complete compatible versions, activates the exact result, and refreshes shims.
Shims do not download missing versions during normal command dispatch. That keeps node, pnpm, and other commands deterministic once a build starts.
Verify the project
doctor reports invalid configuration, missing versions, incomplete installs, PATH precedence, cache readiness, proxy and certificate findings, and plugin issues.
Commit the right files
Commit:Add CI
The same project file works in automation:A prepared project has committed requirements, a successful
jolter sync, a
clean jolter doctor, and CI that calls jolter setup-ci before
package-manager commands.