Node.js

Fased recommends Node 24 and supports Node 22.14 or newer with the built-in node:sqlite module. The installer script can install Node automatically on common VPS and workstation families: Ubuntu, Debian, Kali, Fedora, CentOS, AlmaLinux, Rocky Linux, CloudLinux, Oracle Linux, Amazon Linux, openSUSE, SLES, Alpine, Arch, FreeBSD, WSL2 Ubuntu, and macOS with Homebrew. Use this page when you want to set up Node yourself or debug PATH/runtime issues.

Check your version

node -v
node -e 'require("node:sqlite"); console.log("node:sqlite ok")'

If this prints v24.x or v22.14.x or higher and node:sqlite ok, you are set. If Node is missing, too old, or missing node:sqlite, pick an install method below. Some custom/version-manager Node builds can report a new version but still omit node:sqlite; those are not suitable for full memory support.

Install Node

Homebrew (recommended). If Homebrew already exists, ./install.sh can use it automatically.

brew install node

Or download the macOS installer from nodejs.org.

Use this for Ubuntu, Debian, or Kali:

curl -fsSL https://deb.nodesource.com/setup_24.x | sudo -E bash -
sudo apt-get install -y nodejs

If NodeSource does not yet support a brand-new Ubuntu/Debian codename, install the distro packages and keep the node:sqlite verification step:

sudo apt-get update
sudo apt-get install -y nodejs npm
node -e 'require("node:sqlite"); console.log("node:sqlite ok")'

sudo dnf install -y nodejs24-bin nodejs24-npm-bin

Use this for CentOS, AlmaLinux, Rocky Linux, CloudLinux, Oracle Linux, or Amazon Linux:

curl -fsSL https://rpm.nodesource.com/setup_24.x | sudo bash -
sudo dnf install -y nodejs

Use yum instead of dnf on older images.

Use this for openSUSE or SLES:

sudo zypper --non-interactive install --no-recommends nodejs24 npm24

sudo apk add --no-cache nodejs npm

sudo pacman -Sy --needed nodejs npm

sudo pkg install -y node24 npm-node24

Do not install Node with winget, Chocolatey, or a native Windows Node.js installer for the public Fased runtime. Install WSL2 Ubuntu, open the Ubuntu shell, and use the Ubuntu instructions in this page or let install.sh install Node automatically. Native Windows Node.js cannot run the Unix-socket wallet signer path, and the published npm package rejects native Windows with EBADPLATFORM. Do not force installation with npm platform overrides. See Windows (WSL2).

If Node 24 packages are unavailable for your OS, use Node 22.14 or newer with node:sqlite, install Node 24 from your preferred trusted package source, or use a version manager.

Using a version manager (nvm, fnm, mise, asdf)

Version managers let you switch between Node versions easily. Popular options:

fnm — fast, cross-platform
nvm — widely used on macOS/Linux
mise — polyglot (Node, Python, Ruby, etc.)

Example with fnm:

fnm install 22
fnm use 22

Make sure your version manager is initialized in your shell startup file (~/.zshrc or ~/.bashrc). If it is not, new terminal sessions may not find fased because PATH does not include Node’s bin directory.

Troubleshooting

`fased: command not found`

macOS and explicit source installs write a small repo-backed launcher to ${FASED_CLI_BIN_DIR:-$HOME/.local/bin}/fased. Supported Linux Local and VPS Hosting installs use the prebuilt runtime under ~/.fased/install-cache/npm-global/bin/fased. This error usually means the relevant bin directory is not on your PATH, or your shell has not reloaded its startup files yet.

Check for the launcher

ls -l "$HOME/.local/bin/fased"

Check if it's on your PATH

echo "$PATH"

Look for $HOME/.local/bin in the output. If you used FASED_CLI_BIN_DIR, look for that directory instead.

Add it to your shell startup file

macOS / Linux
Windows / WSL2

Add to ~/.zshrc or ~/.bashrc:

export PATH="$HOME/.local/bin:$PATH"

Then open a new terminal (or run rehash in zsh / hash -r in bash).

Advanced: npm global prefix problems

The public install path is the Fased curl installer. Hosted installs may use the published npm package internally under ~/.fased/install-cache/npm-global. If you are debugging a maintainer/package test and see EACCES errors from a manual npm global install, switch npm’s global prefix to a user-writable directory:

mkdir -p "$HOME/.npm-global"
npm config set prefix "$HOME/.npm-global"
export PATH="$HOME/.npm-global/bin:$PATH"

Add the export PATH=... line to your ~/.bashrc or ~/.zshrc to make it permanent.

Install overview

Alternative methods

Maintenance

Hosting and deployment

Unsupported archives

Advanced and reference

Node.js

Node.js

Check your version

Install Node

Troubleshooting

`fased: command not found`

Advanced: npm global prefix problems

​Node.js

​Check your version

​Install Node

​Troubleshooting

​fased: command not found

​Advanced: npm global prefix problems

Node.js

Check your version

Install Node

Troubleshooting

`fased: command not found`

Advanced: npm global prefix problems