Node.js Cheat Sheet
Practical Node.js cheat sheet with setup steps, core workflows, debugging, and copy-paste examples.
nodejs node-js terminal commands productivity
Node.js cheat sheet with real commands and snippets for setup, core workflows, debugging, and production-safe automation patterns. If you are working across tools, pair this with the Bun Cheat Sheet and Nix Cheat Sheet.
Setup and Installation
Goal: Verify installation and CLI metadata
# Resolve command path from current shell
command -v node
# Print installed version to confirm runtime
node --version
# Read top-level help before using subcommands
node --help
Goal: Install or upgrade the tool on a workstation
# Install package with Homebrew on macOS
brew install node
# Upgrade to the latest available package
brew upgrade node
# Re-check version after upgrade
node --version
Goal: Run day-to-day commands
# Run a Node.js script
node src/index.js
# Start REPL for quick experiments
node
# Watch and restart script on changes
node --watch src/index.js
# Run built-in Node test runner
node --test
Core Workflows
Goal: Capture command help for quick offline lookup
# Create docs folder for generated command references
mkdir -p docs/cli
# Write help output to a timestamped file
node --help > docs/cli/nodejs-help.txt
# Search help output for a keyword
rg "config|auth|deploy" docs/cli/nodejs-help.txt
Goal: Wrap repetitive commands in a script
# Create scripts directory for local automation
mkdir -p scripts
# Write repeatable health-check script
cat > scripts/check-nodejs.sh <<'SH'
#!/usr/bin/env bash
set -euo pipefail
node --version
node --help >/dev/null
SH
# Make script executable and run it
chmod +x scripts/check-nodejs.sh && ./scripts/check-nodejs.sh
Configuration and Environment
Goal: Pin environment variables for predictable runs
# Define environment profile for local commands
export NODEJS_PROFILE=dev
# Persist profile in local shell configuration
echo 'export NODEJS_PROFILE=dev' >> ~/.zshrc
# Reload shell profile changes
source ~/.zshrc
Automation and CI
Goal: Add tool checks to CI pipeline
# Run lint/test/build in strict mode
set -euo pipefail
# Verify CLI exists before invoking workflow
command -v node
# Exit quickly if command is unavailable
node --version
Debugging and Troubleshooting
Goal: Collect diagnostics when commands fail
# Capture command output and exit code
node --help > /tmp/nodejs-debug.log 2>&1; echo $?
# Inspect captured diagnostics
tail -n 80 /tmp/nodejs-debug.log
# Check current shell PATH entries
echo $PATH | tr ':' '\n'
Common Gotchas
- Pin Node.js versions in CI so local and pipeline behavior match.
- Check tool authentication context before running write or deploy commands.
- Prefer non-interactive flags in scripts to avoid stalled jobs.
- Capture stderr logs in CI artifacts for faster incident triage.
- Keep secrets in environment variables, not committed scripts.
Related Sheets
- Bun Cheat Sheet — daily Bun commands and production-ready examples.
- Nix Cheat Sheet — daily Nix commands and production-ready examples.
- Express Cheat Sheet — daily Express commands and production-ready examples.
Related Cheat Sheets
Bun Cheat Sheet
Practical Bun cheat sheet with setup steps, core workflows, debugging, and copy-paste examples.
Express Cheat Sheet
Practical Express cheat sheet with setup steps, core workflows, debugging, and copy-paste examples.
Nix Cheat Sheet
Practical Nix cheat sheet with setup steps, core workflows, debugging, and copy-paste examples.