rule-nodejs

To enforce Node.js project conventions and prevent misconfigurations, you must load mandatory rules before project creation. This guides you to clone an approved boilerplate, remove the original Git history, and use pnpm for dependency management.

The best way to set up a consistent TypeScript boilerplate is to clone an approved template and remove its .git directory. This ensures a clean starting point while enforcing standardized project setup conventions across your team.

Yes, you need to use pnpm for dependency installation in a standardized Node.js project. Enforcing pnpm defines safe post-install handling rules and reduces risk, ensuring consistent dependency workflows across the entire team.

Removing the Git history when cloning a Node.js boilerplate allows you to start clean with your own version control. It severs ties to the original template repository while retaining the approved coding standards and project configuration.

You need to load mandatory coding standards before any Node.js project creation, initialization, or package installation. This ensures the conventions are applied upfront to prevent misconfigurations from the very beginning of your workflow.