
I replaced Morgan with reqlog and never looked back
Let me describe a debugging session I had six months ago. It is 11pm. A client is reporting that their order confirmation emails are not sending. I am staring at a NestJS backend with 12 services and I have no idea which request is failing or what payload it is carrying when it does. My terminal is a wall of Morgan output that looks like this: POST /api/orders 200 43ms GET /api/users/17 200 12ms POST /api/orders 500 8ms GET /api/notifications 200 29ms Something sent a POST /api/orders and got a 500. That is all I know. What was in the body? What did the response say? Which user triggered it? Morgan has no idea. Morgan does not care. Morgan logged a status code and went home. I spent 45 minutes adding console.log(req.body) statements across three files, redeploying, asking the client to reproduce the issue, and squinting at my terminal. I found the bug — a malformed recipientEmail field — in the most embarrassing way possible. That night I started building reqlog. What is wrong with Mor
Continue reading on Dev.to Webdev
Opens in a new tab




