nodejs-best-practices

Choosing a Node.js framework depends on project context like edge, serverless, enterprise, or legacy environments. This skill provides a decision framework for framework selection, evaluating runtime considerations and specific architectural constraints.

Node.js architecture best practices recommend structured layering using controller, service, and repository patterns. This skill guides teams in applying these architectural layers to maintain separation of concerns in backend services and REST APIs.

Choosing between ESM and CommonJS involves evaluating your Node.js runtime and module system requirements. This skill offers runtime and module-system recommendations to help decide the best approach for your backend architecture.

Error handling and validation in Node.js REST APIs require consistent architectural patterns to avoid anti-patterns. This skill provides decision-oriented guidelines for implementing robust security controls, data validation, and centralized error handling.

Yes, this Node.js architecture guidance explicitly applies to serverless environments. It supports decision frameworks for async patterns, security controls, and framework choices tailored to the constraints of serverless Node.js deployments.

Testing strategies in Node.js should avoid common anti-patterns that compromise reliability. This skill outlines practical decision checklists for testing, async patterns, and governance to ensure consistent practices across your team.