goldbergyoni/nodebestpractices
A curated, frequently-updated list of Node.js best practices — code structure, error handling, testing, security, performance, production-readiness.
What it is
A community-maintained reference of ~80 Node.js best practices grouped by category (project structure, error handling, code patterns, testing, going to production, security, performance). Each practice has a TL;DR + an explanation + code examples. CC-BY-SA-4.0 licensed. Translated into ~10 languages.
Key features
- 80+ practices across project structure, error handling, code style, testing, security, performance, production.
- Each entry: short rule + detailed explanation + code examples.
- Frequently refreshed for new Node versions and ecosystem changes.
- Multi-language translations (Brazilian Portuguese, Chinese, French, German, Hebrew, Japanese, Korean, Polish, Russian, Spanish, Turkish).
- CC-BY-SA-4.0 license.
Tech stack
- Markdown content; Dockerfile at the language tag is for repo-level CI.
- Code examples in JavaScript (Node.js).
When to reach for it
- You're a Node.js engineer auditing your codebase against community standards.
- You're a tech lead defining team coding standards.
- You're new to Node.js and want a structured "what to know" reference.
When not to reach for it
- You want a textbook-style introduction — try official Node docs first.
- You want framework-specific practices (NestJS, Express) — coverage is Node-general, not framework-deep.
Maturity signal
105k stars, 11k forks, CC-BY-SA-4.0, actively maintained. 8+ years. Open-issues count of 128 is low. The CC-BY-SA-4.0 license is unusually permissive for a best-practices guide.
Alternatives
- Official Node.js docs — for canonical reference.
airbnb/javascript— for style-guide-specific recommendations.
Tags
awesome-list, nodejs, javascript, best-practices, education, creative-commons, learn-to-code