finds.dev

goldbergyoni/nodebestpractices

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

View on GitHubHomepage ↗

★ 105,642DockerfileCC-BY-SA-4.0updated Jun 2026

// the take

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.

We read the README, the directory tree and a key source file in September 2026. Nobody pays to be listed. How we judge →

// at a glance

Stars
105,642
Forks
10,728
Language
Dockerfile
License
CC-BY-SA-4.0
Last commit
15 Jun 2026

// nearby

If nodebestpractices isn't quite it.

All repos →