Troubleshooting
7 items tagged with "troubleshooting"
FAQs7
What are common errors when running the CLI on Windows?
Common issues: 'node' is not recognized (Node.js not in PATH — restart terminal or reinstall). Execution policy errors in PowerShell (run Set-Executio...
What are common errors when running the CLI on macOS?
Common issues: 'command not found: vibgrate' (package not installed globally or npx not used). Permission denied (use sudo cautiously or fix with sudo...
How do I fix permission denied errors on macOS?
For npm global packages: avoid sudo, instead fix ownership with sudo chown -R $(whoami) ~/.npm and sudo chown -R $(whoami) /usr/local/lib/node_modules...
How do I fix permission denied errors on Windows?
Run terminal as Administrator (right-click > Run as Administrator). For persistent issues: check folder permissions (Properties > Security tab), ensur...
I'm getting Node.js version errors. What should I do?
Vibgrate requires Node.js >= 22.0.0. Check your version: node --version. If too old, upgrade using nvm (nvm install 22), Homebrew (brew upgrade node),...
The scan says lockfile not found. Is that a problem?
Lockfile warnings indicate you don't have a package-lock.json, yarn.lock, pnpm-lock.yaml, or bun.lockb. This affects dependency graph analysis and dup...
I'm getting network timeout errors during scans. How do I fix this?
Network timeouts usually occur when querying package registries. Solutions: increase timeout with --timeout 60000, reduce concurrency with --concurren...