Skip to main content

​
Node.js

Fased recommends Node 24 and supports Node 22.14 or newer with the built-in node:sqlite module. The installer script will detect and install Node automatically — this page is for when you want to set up Node yourself and make sure everything is wired up correctly.

​
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’re good. If Node isn’t installed, the version is too old, or node:sqlite is missing, 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):
brew install node
Or download the macOS installer from nodejs.org.
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 isn’t, fased may not be found in new terminal sessions because the PATH won’t include Node’s bin directory.

​
Troubleshooting

​
fased: command not found

The public installer does not depend on a global npm package. It writes a small repo-backed launcher to ${FASED_CLI_BIN_DIR:-$HOME/.local/bin}/fased. This error usually means that directory is not on your PATH, or your shell has not reloaded its startup files yet.
1

Check for the launcher

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

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.
3

Add it to your shell startup file

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

Direct npm global installation is not the public setup path yet. This only matters if you are doing your own package-manager experiment or installing a skill dependency with npm. If you see EACCES errors from a manual npm install -g, 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.