Best Fixes
Check whether Node is installed at all and whether your shell session loaded your version manager correctly.
If this happens in CI or scripts, verify PATH setup there separately from your local terminal.
Error Fix
How to Fix 'node: command not found'
A quick path to diagnosing missing Node.js commands in shells and automation.
This usually means Node is not installed, the shell PATH is wrong, or a version manager has not been initialized in the current environment. CI and shell startup files are common sources of mismatch.
Avoid This
Do not assume local terminal success means your CI environment is configured the same way.
Do not paper over version-manager setup issues with ad hoc symlinks unless you know you want that system-wide behavior.
Save commands, add notes, and build a Cheatbook with the fixes you want to keep handy.