One fast, reliable home for your JavaScript runtimes and tools.
Jolter keeps Node.js, Bun, Deno, npm, pnpm, and Yarn consistent across your machine, your team, and CI. Pin what a project needs once, enter the directory, and use the right toolchain without manually switching versions.
Run in PowerShell:
irm https://jolter.dev/install.ps1 | iexRun in a terminal:
curl -fsSL https://jolter.dev/install.sh | shThen finish shell setup:
jolter setupApply the command Jolter prints, restart your terminal, and verify everything:
jolter doctorSee the installation guide for manual installation, checksums, source builds, upgrades, and platform details.
Install the runtime you want:
jolter use node@ltsAdd the tools you prefer:
jolter use pnpm@10
jolter use yarn@4Pin the project so everyone gets the same setup:
cd my-project
jolter pin node@24
jolter pin pnpm@10
jolter syncJolter creates a small jolter.json file that can be committed with the
project. Team members and CI can then reproduce the toolchain with one command.
Jolter automatically selects project versions through lightweight command
shims. Move between repositories and node, pnpm, yarn, bun, and deno
follow the project you are working in.
The same commands work on Windows, macOS, Linux, and WSL. Jolter understands
its own project file as well as .node-version, .nvmrc, and
package.json#packageManager.
jolter sync prepares a developer machine. jolter setup-ci prepares an
automation job and exposes the resolved runtime, tools, shims, and cache
location.
jolter doctor checks the project, installed versions, command routing,
storage, network configuration, and offline readiness, then gives practical
remediation steps.
Jolter downloads from official providers, verifies release integrity, rejects insecure redirects, extracts into temporary locations, and publishes complete installations atomically.
| Category | Supported |
|---|---|
| Runtimes | Node.js, Bun, Deno |
| Tools | npm, pnpm, Yarn |
| Platforms | Windows x64, Linux x64, macOS x64, macOS ARM64, WSL |
| Shells | PowerShell, Command Prompt, Bash, Zsh, Fish |
Tools run through the selected Node.js version, so Jolter also checks their declared Node.js compatibility before activation.
{
"$schema": "https://schemas.jolter.dev/project/v2/schema.json",
"schemaVersion": 2,
"runtime": {
"node": "24.x"
},
"tools": {
"pnpm": "10.x",
"yarn": "4.x"
}
}A project can select one runtime and multiple tools. Selectors can describe an
exact version, a release line such as 24 or 24.x, latest, or Node.js
lts.
Learn more in configuration and project resolution.
# Install and activate
jolter use node@lts
jolter use pnpm@10
# Save project requirements
jolter pin node@24
jolter pin pnpm@10
# Reproduce or repair a project
jolter sync
jolter repair
# Update active versions
jolter update node
jolter update --all
# Inspect health and installed versions
jolter doctor
jolter list
# Safely reclaim space
jolter prune --dry-run
jolter cache statusSee the complete command reference for every command, argument, output mode, and exit behavior.
Jolter automatically switches to stable line-oriented logs when output is redirected or a CI environment is detected.
jolter setup-ci --no-progress
jolter setup-ci --json --no-colorUse --quiet for final results only, --verbose for transfer details, and
--no-progress for deterministic logs. Machine-readable output is available
for inventory, diagnostics, and CI setup.
Read the CI guide and output and automation reference.
Start at the documentation home.
- Getting started
- Installation
- Command reference
- Configuration
- Runtimes and tools
- Shell setup and automatic switching
- CI integration
- Environment variables
- Diagnostics
- Troubleshooting
- Security model
- Architecture
Jolter 0.3.0 provides the stable core command surface and remains pre-1.0
while its cross-platform release and real-provider workflows complete a
release-candidate period. Compatibility commitments and known release work are
documented in the compatibility policy and
roadmap.
Jolter is open source under the MIT License.