Using plugins - Jolter

Use plugins.jolter.dev to search the public registry. A plugin page shows the canonical name, approved alias when one exists, repository, README, latest version, and install command.

Install a plugin

Install by approved alias:

jolter plugin install eslint

Install by canonical scoped name and provider selector:

jolter plugin install @eslint/eslint@1

add and i are aliases for install:

jolter plugin add eslint
jolter plugin i @eslint/eslint@1

During installation, Jolter resolves the name through the registry, downloads the selected release manifest and WASM entrypoint, verifies integrity metadata, stores the plugin under JOLTER_HOME/plugins, and refreshes shims for the plugin commands.

List installed plugins

jolter plugin list
jolter plugin list --json

The human output is for interactive use. Automation should use --json and rely on field names and exit status.

Use plugin-provided tools

After installing a provider, use the tool like any other Jolter-managed tool:

jolter use eslint@8
eslint --version

Pin a plugin-provided tool into the current project:

jolter pin eslint@8
jolter sync

When Jolter can identify the provider, pin records both the tool requirement and the provider requirement in jolter.json.

Sync projects with plugins

Projects that declare plugins require those providers before plugin tools can be resolved.

jolter sync

Without --yes, Jolter verifies required plugins are already installed. Missing plugins fail with remediation text. Allow Jolter to install missing declared plugins:

jolter sync --yes
jolter setup-ci --yes

Use --yes only after the plugin requirements have been reviewed.

Update plugins

Update one installed plugin:

jolter plugin update eslint

Update every installed plugin:

jolter plugin update --all

up is an alias:

jolter plugin up eslint

Plugin updates move the provider version. Plugin-provided tool updates still use jolter update:

jolter update eslint
jolter update eslint@latest

Uninstall plugins

jolter plugin uninstall eslint

remove and rm are aliases:

jolter plugin remove eslint
jolter plugin rm eslint

If the plugin still owns active shims or tool state, Jolter can refuse removal. Use --force only when you intentionally want to remove the provider anyway:

jolter plugin uninstall eslint --force

Resolve provider ambiguity

If multiple installed plugins provide the same tool, declare the intended provider:

jolter.json

{
  "tools": {
    "eslint": "8"
  },
  "plugins": {
    "@eslint/eslint": "1"
  }
}

Then run:

jolter sync
jolter doctor

Registry override

JOLTER_REGISTRY_URL changes the registry used by plugin commands:

export JOLTER_REGISTRY_URL="https://registry.example.com"

PowerShell:

$env:JOLTER_REGISTRY_URL = "https://registry.example.com"

Run jolter doctor in the same shell to confirm the active configuration.

​Install a plugin

​List installed plugins

​Use plugin-provided tools

​Sync projects with plugins

​Update plugins

​Uninstall plugins

​Resolve provider ambiguity

​Registry override