nodejs-best-practices_skill

Overview

This skill teaches Node.js decision-making and development principles for 2025, emphasizing thinking over copying code. It covers framework selection, runtime choices, architecture, async patterns, validation, security, and testing. The goal is to help you pick the right trade-offs for your specific project. Guidance is practical and context-driven rather than prescriptive code snippets.

How this skill works

I guide you through targeted questions about deployment target, team familiarity, performance needs, and growth expectations to recommend frameworks and runtime patterns. I explain layered architecture, error handling, and async strategies so you can design testable and maintainable systems. Security, validation, and testing checklists help you bake safety and reliability into decisions from the start.

When to use it

• Choosing a framework for a new API, serverless function, or full-stack app
• Deciding between ESM/CommonJS or runtime (Node, Bun, Deno) for a project
• Designing an architecture that must scale or remain flexible
• Planning error handling, observability, and validation strategies
• Preparing security and testing priorities before implementation

Best practices

• Ask context questions before defaulting to a familiar stack
• Use layered structure (controller → service → repository) for growth and testability
• Validate at boundaries and fail fast with clear error codes
• Prefer async/await for sequential flows and Promise patterns for parallelism; offload CPU work to workers
• Treat secrets, CORS, and rate limiting as requirements, and log full context without leaking internals

Example use cases

• Edge-optimized serverless API: choose Hono for minimal cold starts and native edge deployments
• High-performance JSON API: pick Fastify when throughput and low latency matter
• Enterprise service with DI and structure: use NestJS for teams needing conventions and scalability
• Prototyping or scripts: run TypeScript natively in Node 22+ for faster iteration
• Migration planning: keep repository layer isolated to swap databases with minimal business logic changes