Node.js Best Practices
Follow us on Twitter! @nodepractices
Read in a different language: CN, BR, RU, PL (ES, FR, HE, KR and TR in progress!)
Built and maintained by our Steering Committee and Collaborators
Latest Best Practices and News
:tada: Node.js best practices reached 40k stars: Thank you to each and every contributor who helped turning this project into what it is today! We've got lots of plans for the time ahead, as we expand our ever-growing list of Node.js best practices even further.
:rocket: Two New Best Practices: We've been working hard on two new best practices, a section about using npm ci to preview the dependency state in production environments and another on testing your middlewares in isolation
:whale: Node.js + Docker best practices: We've opened a call for ideas to collect best practices related to running dockerized Node.js applications. If you've got any further best practices, don't hesitate to join the conversation!
Welcome! 3 Things You Ought To Know First
1. You are, in fact, reading dozens of the best Node.js articles - this repository is a summary and curation of the top-ranked content on Node.js best practices, as well as content written here by collaborators
2. It is the largest compilation, and it is growing every week - currently, more than 80 best practices, style guides, and architectural tips are presented. New issues and pull requests are created every day to keep this live book updated. We'd love to see you contributing here, whether that is fixing code mistakes, helping with translations, or suggesting brilliant new ideas. See our writing guidelines here
3. Most best practices have additional info - most bullets include a **