How to Node.js - Part 2
summary
npm holds 2 million modules so popularity alone misleads: expect many poor performers and surprises (Ramda and Mongoose cause performance and hidden I/O problems; Bluebird is now obsolete). Prefer lightweight, maintained tools: undici 1.5M/week for HTTP, pino for newline-delimited JSON logging, ajv for JSON Schema, dotenv for env, fastify for servers. Use tap/mocha over Jest for Node testing due to runtime incompatibilities. Node supports worker threads; build small CLIs via npm bin. Overall choose libraries by maintenance, deps and measured performance.
AI-written summary · about
chapters (13)
- 0:00Introduction and ecosystem overview
- 1:24NPM module selection pitfalls
- 9:31Library evaluation criteria
- 17:56Logging and debugging in Node.js
- 27:07Node.js threading and worker threads
- 28:34Data validation with AJV
- 32:09Choosing HTTP clients
- 38:17Testing strategies and frameworks
- 51:32Why avoid Jest for testing
- 1:08:42Building CLI tools
- 2:05:00Environment variables and configuration
- 2:12:49Contributing to Node.js
- 2:18:04Node.js certifications overview
