jolter.json. Schema version 2 supports one runtime, multiple tools, and optional plugin requirements.
Complete schema example
jolter.json
sync, repair, and setup-ci require a resolvable runtime from jolter.json, .node-version, or .nvmrc.
Top-level fields
| Field | Type | Meaning |
|---|---|---|
$schema | string | Optional JSON Schema URL |
schemaVersion | integer | Current schema version, 2 |
runtime | object | Zero or one of node, bun, or deno |
tools | object | Built-in tools and plugin-provided tools |
plugins | object | Plugin provider requirements |
Runtime rules
Valid:Tool rules
Built-in tools:Legacy input compatibility
Schema version 1 and the earlier map-valuedpackageManager key remain accepted as input compatibility. When Jolter rewrites configuration, it emits the canonical tools key.
This is different from the standard string-valued package.json#packageManager field:
package.json
Creating and updating config
Usepin:
jolter.json. Do not commit JOLTER_HOME or installed runtime directories.