squad-conventions

To establish Node.js coding conventions for a CLI tool with zero dependencies, use only Node.js built-ins for a lightweight runtime. This approach maintains codebase consistency and reduces external library overhead.

The best way to handle errors consistently in a Node.js CLI application is to implement a dedicated fatal() function. This pattern standardizes error reporting and robust handling across the entire codebase.

You test a Node.js CLI tool without external frameworks by utilizing the built-in node:test runner and node:assert/strict module. These native modules provide streamlined testing patterns for robust validation and zero-dependency development.

Yes, a zero-dependency Node.js CLI tool can ensure Windows compatibility by following specific file structure and operational guidelines. This includes implementing robust file handling and initialization patterns to support different operating systems.

To implement robust recursive file copying using only Node.js built-ins, define a copyRecursive() function. This pattern provides reliable file and directory handling without relying on external libraries.

CLI initialization needs to be idempotent to maintain the integrity of user state during repeated initialization processes. This prevents accidental data overwrites and ensures consistent setup operations.