finds.dev← search

// the find

goldbergyoni/nodebestpractices

★ 105,642 · Dockerfile · CC-BY-SA-4.0 · updated Jun 2026

✅ The Node.js best practices list (July 2026)

A living, community-maintained checklist of 100+ Node.js best practices covering architecture, error handling, code style, testing, security, and Docker. It's aimed at intermediate-to-senior Node developers who want a reference to audit an existing codebase against, not a tutorial for beginners.

The advice is grounded in real production pain rather than generic platitudes — distinguishing operational vs. programmer errors and the unhandled-promise-rejection section both reflect actual failure modes people hit. Each item follows a consistent TL;DR + rationale + 'read more' structure, so it works both as a skim and a deep dive. Coverage is broad and kept current (Node 22, the node: protocol, npm ci) rather than frozen at some 2018 snapshot. It's translated into a dozen-plus languages with real ongoing PR activity, not a solo opinion dump.

It's a document, not code — there's no runnable reference implementation in this repo itself (the linked Practica.js starter lives elsewhere), so you can't clone it and see the practices applied. Advice quality is uneven: trivial style nits like curly-brace placement sit next to genuinely strategic calls like component-based architecture, with only an informal #strategic tag to tell them apart. The framework recommendations (Nest.js vs Fastify vs Koa vs Express) are one consultant's take and will age faster than the rest of the content. Being doc-only, there's no test suite validating any of the claims — correctness rests entirely on manual review and PR scrutiny.

View on GitHub → Homepage ↗

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →