> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wednesdayai.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Node.js

# Node.js

WednesdayAI requires **Node 24 or newer**. The [installer script](https://docs.wednesdayai.dev/next/admin/install#install-methods) 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 (versions, PATH, global installs).

## Check your version

```bash theme={"dark"}
node -v
```

If this prints `v24.x.x` or higher, you're good. If Node isn't installed or the version is too old, pick an install method below.

## Install Node

> [tab] macOS
>
> **Homebrew** (recommended):
>
> ```bash theme={"dark"}
> brew install node
> ```
>
> Or download the macOS installer from [nodejs.org](https://nodejs.org/).

> [tab] Linux
>
> **Ubuntu / Debian:**
>
> ```bash theme={"dark"}
> curl -fsSL https://deb.nodesource.com/setup_24.x | sudo -E bash -
> sudo apt-get install -y nodejs
> ```
>
> **Fedora / RHEL:**
>
> ```bash theme={"dark"}
> sudo dnf install nodejs
> ```
>
> Or use a version manager (see below).

> [tab] Windows
>
> **winget** (recommended):
>
> ```powershell theme={"dark"}
> winget install OpenJS.NodeJS.LTS
> ```
>
> **Chocolatey:**
>
> ```powershell theme={"dark"}
> choco install nodejs-lts
> ```
>
> Or download the Windows installer from [nodejs.org](https://nodejs.org/).

> [accordion] Using a version manager (nvm, fnm, mise, asdf)
>
> Version managers let you switch between Node versions easily. Popular options:
>
> * [**fnm**](https://github.com/Schniz/fnm) — fast, cross-platform
> * [**nvm**](https://github.com/nvm-sh/nvm) — widely used on macOS/Linux
> * [**mise**](https://mise.jdx.dev/) — polyglot (Node, Python, Ruby, etc.)
>
> Example with fnm:
>
> ```bash theme={"dark"}
> fnm install 24
> fnm use 24
> ```
>
> > [!WARNING]
> >
> > Make sure your version manager is initialized in your shell startup file (`~/.zshrc` or `~/.bashrc`). If it isn't, `openclaw` may not be found in new terminal sessions because the PATH won't include Node's bin directory.

## Troubleshooting

### `openclaw: command not found`

This almost always means npm's global bin directory isn't on your PATH.

**1. Find your global npm prefix**

```bash theme={"dark"}
npm prefix -g
```

**2. Check if it's on your PATH**

```bash theme={"dark"}
echo "$PATH"
```

Look for `<npm-prefix>/bin` (macOS/Linux) or `<npm-prefix>` (Windows) in the output.

**3. Add it to your shell startup file**

> [tab] macOS / Linux
>
> Add to `~/.zshrc` or `~/.bashrc`:
>
> ```bash theme={"dark"}
> export PATH="$(npm prefix -g)/bin:$PATH"
> ```
>
> Then open a new terminal (or run `rehash` in zsh / `hash -r` in bash).

> [tab] Windows
>
> Add the output of `npm prefix -g` to your system PATH via Settings → System → Environment Variables.

### Permission errors on `npm install -g` (Linux)

If you see `EACCES` errors, switch npm's global prefix to a user-writable directory:

```bash theme={"dark"}
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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.