Node

Commands

Command	Description
lerd node:install <version>	Install a Node.js version globally via fnm
lerd node:uninstall <version>	Uninstall a Node.js version via fnm
lerd node:use <version>	Set the global default Node.js version
lerd isolate:node <version>	Pin Node version for cwd: writes .node-version, runs fnm install

---

Usage

lerd install places shims for node, npm, and npx in ~/.local/share/lerd/bin/, which is added to your PATH. You use them exactly as you normally would, lerd picks the right version automatically:

node --version
npm install
npx tsc --init

---

Version resolution

1. .lerd.yaml: node_version field (explicit lerd override, highest priority)
2. .nvmrc in the project root
3. .node-version in the project root
4. package.json: engines.node field
5. Global default in ~/.config/lerd/config.yaml

To pin a project to a specific version:

cd ~/Lerd/my-app
lerd isolate:node 20
# writes .node-version and installs Node 20 via fnm

To install a version without pinning a project:

lerd node:install 22

---

Default version

lerd node:use <version> sets the global default and stores it in ~/.config/lerd/config.yaml. Sites without a pinned version use this default.

lerd node:use 22

Version numbers are normalised to the major only, so 22.11.0 and 22.14.1 are both treated as 22, and only one entry per major appears in the UI and CLI.

---

fnm

Node version management is handled by fnm, which is bundled and installed automatically. The node, npm, and npx shims in ~/.local/share/lerd/bin/ invoke the correct version via fnm for each project.

---

System-managed vs lerd-managed Node

If lerd install detects an existing node, npm, or npx on your PATH or under a known version-manager directory (nvm, volta, mise, asdf, fnm), it asks "Let lerd manage Node.js?" before writing any shims.

• Answer yes: lerd installs fnm, picks the current LTS, sets it as the fnm default, and writes the node / npm / npx shims into ~/.local/share/lerd/bin/. Per-project version pinning works as described above.
• Answer no: lerd writes nothing into ~/.local/share/lerd/bin/, removes any stale shims from a previous opt-in, and stays out of your PATH. Sites use whatever node your shell resolves; per-project pinning is your version manager's job. The dashboard's Node tab disables the install controls and points back at lerd install if you change your mind.

lerd node:install / node:use / node:uninstall warn and require confirmation if you run them on a host where lerd isn't currently managing Node, and write fresh shims on accept so CLI opt-in matches the install flow.