What problem does it solve?
Deployers need consistent Node.js 22 code that avoids legacy callbacks, mismanaged streams, and runtime pitfalls, so harnessing modern async, error, and runtime APIs prevents crashes and unpredictable behavior.
Core Features & Use Cases
- Module conventions: Enforce full ESM usage, prefer named exports, and rely on import.meta utilities instead of __dirname/__filename to keep modules maintainable.
- Async and error handling: Favor async/await, Promise.all for parallel tasks, top-level handlers, and typed AppError classes so failures surface clearly.
- Streams, env, performance, and security: Recommend stream.pipeline, Web Streams, strict environment validation, worker_threads for CPU work, structured logging, crypto utilities, and NODE_ENV=production to stay efficient and safe.
- Use case: Review a Node.js server handler, script, or utility in this project to confirm it follows these async, stream, and config safeguards before deployment.
Quick Start
Ask the Node.js 22 best practices skill to evaluate the new server route for async, stream, and environment compliance before merging the change.