Repository navigation
docs: Troubleshooting section tells users to check PATH but doesn't show how to fix it #1458
Description
Problem
After running npm install -g @bradygaster/squad-cli, the squad command is not found on Windows when the npm global prefix is set to a custom directory (e.g. ~/.npm-global). The current troubleshooting section in the installation docs tells users to check their PATH but never explains how to actually fix it.
Steps to reproduce
- Have a custom npm prefix (e.g.
npm config set prefix ~/.npm-global) - Run
npm install -g @bradygaster/squad-cli— installs successfully - Run
squad—squad: The term 'squad' is not recognized
Expected
The troubleshooting section should provide the actual fix commands for each platform (adding npm prefix -g to PATH), not just diagnostic commands.
Suggested fix
Update the squad: command not found troubleshooting section to include:
- The
npm prefix -gcommand to find the actual global bin directory - Platform-specific instructions for adding it to PATH (bash/zsh profile for macOS/Linux,
[Environment]::SetEnvironmentVariablefor Windows)
Activity
omercangumus commentedon Jul 16, 2026
taking this — the installation page's "command not found" entry says Fix: but only shows diagnostics (and the Windows line is cmd syntax, findstr %PATH%, which won't run in PowerShell). Will add npm prefix -g plus the actual per-platform PATH fix, verified live on a Windows machine with a custom prefix.
docs: fix Windows PATH snippet and split shell reload commands
docs: add PATH fix instructions to installation troubleshooting
tamirdresher commentedon Jul 17, 2026
Quick clarifier for anyone landing on this issue: #1488 was closed as a duplicate of this one. The active implementation is #1459 by @johnazariah, which has closing linkage (
Fixes #1458) in its PR body and just picked up a fresh APPROVE from me. Merging that PR will close this issue automatically.docs: add PATH fix instructions to installation troubleshooting (gith…