nodejs-best-practices

Topics in the source

• Node.js Best Practices
• ⚠️ How to Use This Skill
• 1. Framework Selection (2025)
• Decision Tree
• Comparison Principles
• Selection Questions to Ask:
• 2. Runtime Considerations (2025)
• Native TypeScript

Principles and decision-making for Node.js development in 2025. Learn to THINK, not memorize code patterns. -- This skill teaches decision-making principles, not fixed code to copy. ASK user for preferences when unclear Choose framework/pattern based on CONTEXT Don't default to same solution every time -- | Factor | Hono | Fastify | Express | |--------|------|---------|---------| | Best for | Edge, serverless | Performance | Legacy, learning | | Cold start | Fastest | Fast | Moderate | | Ecosystem | Growing | Good | Largest | | TypeScript | Native | Excellent | Good | | Learning curve | Low | Medium | Low | 1. What's the deployment target? 2. Is cold start time critical? 3. Does team have existing experience? 4. Is there legacy code to maintain? -- | Runtime | Best For | |---------|----------| | Node.js | General purpose, largest ecosystem | | Bun | Performance, built-in bundler | | Deno | Security-first, built-in TypeScript | -- Testability: Mock layers independently Flexibility: Swap database without touching business logic Clarity: Each layer has single responsibility Small scripts → Single file OK Prototypes → Less structure acceptable Always ask: "Will this grow?" -- | Situati

This is an excerpt. Refer to the complete source and its current requirements.