refactor: rename clawdbot to moltbot with legacy compat

This commit is contained in:
Peter Steinberger committed 2026-01-27 12:21:02 +00:00
1 parent 83460df96f
commit 6d16a658e5
1839 files changed
+11250 -11199

No files matched your search

+4 -4
View File
@@ -2,16 +2,16 @@
title: "Node.js + npm (PATH sanity)"
summary: "Node.js + npm install sanity: versions, PATH, and global installs"
read_when:
- "You installed Clawdbot but `clawdbot` is “command not found”"
- "You installed Moltbot but `moltbot` is “command not found”"
- "You’re setting up Node.js/npm on a new machine"
- "npm install -g ... fails with permissions or PATH issues"
---
# Node.js + npm (PATH sanity)
Clawdbot’s runtime baseline is **Node 22+**.
Moltbot’s runtime baseline is **Node 22+**.
If you can run `npm install -g clawdbot@latest` but later see `clawdbot: command not found`, it’s almost always a **PATH** issue: the directory where npm puts global binaries isn’t on your shell’s PATH.
If you can run `npm install -g moltbot@latest` but later see `moltbot: command not found`, it’s almost always a **PATH** issue: the directory where npm puts global binaries isn’t on your shell’s PATH.
## Quick diagnosis
@@ -24,7 +24,7 @@ npm prefix -g
echo "$PATH"
```
If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** present inside `echo "$PATH"`, your shell can’t find global npm binaries (including `clawdbot`).
If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** present inside `echo "$PATH"`, your shell can’t find global npm binaries (including `moltbot`).
## Fix: put npm’s global bin dir on PATH