otty / dotfiles

All tools/Volta

Volta

volta

Volta: JS Toolchains as Code. The Hassle-Free JavaScript Tool Manager.

Detected by volta | macOS, Linux, Windows |volta.sh

Sync it volta.toml

Sync rules

What travels, what stays, what never leaves

Volta in your home directory Every rule on this page, by file

· hooks.json Sync

· tools/user/platform.json Sync

· hooks.json Sync

· tools/user/platform.json Sync

Only what the catalog names. A directory that syncs brings everything inside it except what is listed as excluded here.

apps/volta.tomlThe file this page is generated from

id = "volta"

name = "Volta"

homepage = "https://volta.sh"

description = "Volta: JS Toolchains as Code. The Hassle-Free JavaScript Tool Manager."

# The V-and-coils mark from Volta's own assets repository — the same mark

# the wordmark is built around, on its own so it reads at icon size.

icon = "https://raw.githubusercontent.com/volta-cli/assets/main/concepts/tesla-coil/two-coils-straightened-v-only-350x350.png"

detect = ["volta"]

# https://docs.volta.sh/advanced/hooks — "Hooks specified in the Volta

# directory (~/.volta/hooks.json on Linux/MacOS, %LOCALAPPDATA%\Volta\hooks.json

# on Windows) will apply across the entire system"; a project's own

# <PROJECT ROOT>/.volta/hooks.json is not user-level and is not listed.

# crates/volta-layout/src/v3.rs spells out the rest of that directory:

# "cache"/ "bin"/ "log"/ "tmp"/ state, shims and downloads

# "tools"/ "inventory"/ "image"/ "shared"/ installed toolchains

# "tools"/"user"/"platform.json" the default toolchain

# "hooks.json" the hooks file above

# "layout.v3" the layout marker

# platform.json is what `volta install node@22` pins — the user's default

# toolchain, the same kind of fact as asdf's ~/.tool-versions — so it is listed

# beside hooks.json. Everything else is an install or a cache and is left out

# by naming the two files rather than the directory.

paths = [

"~/.volta/hooks.json",

"~/.volta/tools/user/platform.json",

"%LOCALAPPDATA%/Volta/hooks.json",

"%LOCALAPPDATA%/Volta/tools/user/platform.json",

]

exclude = []

# Hooks name registry URLs and templates; platform.json names version numbers.

# Neither authenticates anything — Volta downloads from public registries.

secret = []

# Both files are read at the start of a shim resolution by a process that then

# execs the tool.

side_effect = false

# No machine_lines: a hook can be `{"bin": "…"}`, a command run to resolve a

# version, which would be machine-local when it names an absolute path — but it

# is just as often a bare command name, and a rule on the key would strand the

# `template`/`prefix` hooks that are exactly what a team wants shared.

Use it with your dotfile manager

Same data, in the shape your tool already reads

Opens Otty and adds this tool to what it syncs

Opens otty://sync/add/volta. Otty ships with this catalog, so the link only has to name the tool — nothing is downloaded.

Every one of these is generated from the same rules as this page.