Skip to main content
Jolter keeps Node.js, Bun, Deno, npm, pnpm, Yarn, and plugin-provided tools consistent across your machine, your team, and CI. Pin what a project needs once, enter the directory, and run the right toolchain without manually switching versions.

Start in 5 minutes

Install Jolter, enable shims, select Node.js, pin pnpm, and run a project sync.

Create your first project

Add jolter.json, commit it, and give every contributor the same toolchain.

Automate CI

Use jolter setup-ci today and the planned setup action when it ships.

Build a plugin

Package new ecosystem tools behind verified Jolter plugin commands.

​
Why teams use Jolter

Jolter solves the part of JavaScript tooling that quietly breaks builds: local runtime drift, different package-manager versions, CI jobs that resolve differently from laptops, and command routing that depends on shell state.
ProblemJolter behavior
Developers keep switching Node.js versions by handShims resolve the project on every command invocation
CI installs a different runtime than local developmentjolter.json and jolter setup-ci use the same resolver
Package managers move unexpectedlyTools can be pinned by major, minor, exact version, or verified hash
Missing or broken installations are hard to diagnosejolter doctor reports storage, PATH, project, cache, proxy, and compatibility findings
Tool downloads need verificationRuntime archives and tool tarballs are checked before publication

​
Supported toolchains

CategorySupported
RuntimesNode.js, Bun, Deno
Built-in toolsnpm, pnpm, Yarn
Plugin toolsRegistry-backed tool providers through schema v2 plugins
PlatformsWindows x64, Linux x64, macOS x64, macOS ARM64, WSL
ShellsPowerShell, Command Prompt, Bash, Zsh, Fish

​
The short version

irm https://get.jolter.dev/install.ps1 | iex
jolter setup
jolter use node@lts
jolter use pnpm@10
jolter doctor

curl -fsSL https://get.jolter.dev/install.sh | sh
jolter setup
jolter use node@lts
jolter use pnpm@10
jolter doctor
Then add project requirements: 
jolter pin node@24
jolter pin pnpm@10
jolter sync
Jolter writes a small jolter.json file that belongs in source control:
jolter.json
{
  "$schema": "https://schemas.jolter.dev/project/v2/schema.json",
  "schemaVersion": 2,
  "runtime": {
    "node": "24"
  },
  "tools": {
    "pnpm": "10"
  }
}

​
Documentation map

Guides

Practical workflows for runtimes, tools, monorepos, automatic switching, updates, and team onboarding.

Reference

Exact command syntax, selectors, configuration fields, environment variables, and storage contracts.

Operations

Diagnose broken PATH entries, incomplete installs, cache misses, proxy problems, and lifecycle tasks.

Security

Review Jolter’s trust boundaries, integrity checks, archive safety, plugin verification, and reporting flow.
If you only read one page, use the quickstart. If you are preparing a repository for a team, continue with first project.