Documentation / Troubleshooting

Troubleshoot Devcanon

Resolve installation, path, version, and standards-conflict problems.

Most Devcanon issues come from the current directory, permissions, Node.js versions, or intentionally preserved local files.

Filesystem root error

Devcanon refuses to install into /. Change to your repository or provide an explicit path.

Command not found

Confirm Node.js 20+, reopen the terminal after global installation, or use npx.

Conflict is reported

This is protective behavior, not data loss. Run devcanon update --dry-run, inspect the local standard, and resolve it in a normal code review.

Get help

Include your operating system, Node.js version, Devcanon version, command, and sanitized error output in a GitHub issue. Never publish secrets or proprietary source.