Fix TypeScript path aliases not working in Node.js
tsconfig paths are a compile-time fiction. tsc deletes the types and leaves your @/ imports exactly as written, so Node — which never reads tsconfig — has no idea what @/db means.
Common Node.js errors · quick reference
All error fixes →| Error | What it means / fix |
|---|---|
| — | Fix Prisma connection pool timeout (P2024) in Node.js P2024 usually means Prisma could not get a free connection fast enough. Sometimes the database is overloaded, but more often the app holds connections too long, opens too many clients, or multiplies pools across instances. |
| — | Fix nodemon: command not found A locally installed nodemon is not on your PATH, and it is not supposed to be. Your shell looking for a global binary is the bug, not the missing global install. |
| — | Fix Docker node_modules not found in a Node.js container The image has node_modules. Then your compose bind mount drops your host folder on top of it and hides them. The build was never the problem — the volume was. |
| — | Fix ERR_REQUIRE_ESM in Node.js ERR_REQUIRE_ESM used to mean a painful migration. On Node 22 and 24 it usually means: upgrade Node, because require() can load synchronous ESM — with a small .default tweak for default exports. |
| — | Fix ERR_UNKNOWN_FILE_EXTENSION “.ts” in ts-node ts-node's native ESM support has been a long-running pain point since 2020, and it still isn't reliable. On a type:module project, the cleaner answer is to stop using ts-node. |
| UnhandledRejection | Fix UnhandledPromiseRejection in Node.js It’s 2 a.m., the pager goes off, and your Node 22 service is in a restart loop. The logs show one line — a rejection reason — then… |
Tutorials & how-tos
All tutorials →
Comparisons & benchmarks
All comparisons →
Sequelize vs Prisma vs TypeORM in 2026: the Node.js ORM benchmark and the pick I’d make
I've shipped APIs on all three. Sequelize from 2017 to 2020 on a payments API that's still in production. TypeORM through 2021 on a logistics dashboard, where the migration generator broke twice and burned a sprint each time.…
Performance & Architecture
All recipes →
errors
Recipe
Sentry for Node.js APIs: Express errors, traces, releases
Set up Sentry for Node.js and Express with error capture, tracing, releases, source maps, PII scrubbing, sampling, and production alert hygiene.
Node.js
Recipe
OpenTelemetry in Node.js: production traces that help
OpenTelemetry in Node.js with HTTP, Express or Fastify, pg, Prisma, Redis, request IDs, trace propagation, sampling, and the incident view that matters.
Node.js
Recipe
PostgreSQL connection pooling in Node.js: the bug that shows up at scale
PostgreSQL connection pooling in Node.js with pg, Prisma, PgBouncer, serverless limits, transaction pooling traps, and the dashboard I check first.
Docker
Recipe
Node.js microservices architecture: the patterns that actually held in production
I helped a logistics startup split a Node.js monolith into seven services in 2022 and watched them spend the next eight months untangling a distributed monolith. The services…
Express
Recipe
Node.js API security in 2026: the checklist I run before pushing to prod
I leaked a logistics company’s internal API for eleven days. Not a customer-facing one — an admin endpoint that returned every shipment’s tracking number, recipient address, and carrier…
Node.js
Recipe
Node.js cluster vs worker threads: which one when (and the trap I fell into)
I had a Node.js video-processing API throwing 503s every time someone uploaded a 4K clip. The default fix everyone reaches for — cluster.fork() across cores — actually made…
