Mullionv2.1.1
Using Mullion

Node

Official Node.js builds with global, per-project and .nvmrc versions, an npm version picker, and diagnostics.

Versions

$ mullion node available        # newest of each major
$ mullion node install           # LTS; also "latest", "22" or "22.12.0"
$ mullion node use 22            # the default node/npm on PATH
$ mullion node list              # * = default
$ mullion node uninstall 18

How a folder gets its Node version

node, npm and npx on your PATH are small shims. For the folder you're in, they pick:

  1. the site's pinned version (mullion node isolate 20, or the project page), else
  2. the project's .nvmrc (searched upwards, stopping at your home folder), else
  3. the default version.
$ mullion node which     # explains which version this folder gets, and why
$ mullion node isolate 20
$ mullion node unisolate

If a pinned version isn't installed, Mullion installs it the first time it's needed. mullion node which also detects a foreign Node, such as nvm, that shadows Mullion's and offers to fix it.

npm versions

Each Node install carries its own npm. To change it, use the Change npm… picker on the Node page, or:

$ mullion node npm 10            # for the default Node
$ mullion node npm 10.9.2 20      # for a specific Node install

Diagnostics

The Node page's Diagnostics card shows the same report as mullion node which: which Node resolves, why, and whether another Node on PATH shadows Mullion's.

HTTPS from Node code

Managed dev servers, project commands, workers and project terminals get NODE_EXTRA_CA_CERTS pointing at Mullion's local CA. Server-side code (SSR, API routes) can then call other https://*.test sites without certificate errors.