Logging is essential, but setting it up with Pino often means boilerplate: installing packages, wiring middleware, passing request IDs manually, and configuring redaction yourself. It works, but it’s repetitive.
Blockend Logger takes a different approach. It uses Pino under the hood but generates a ready‑to‑use, type‑safe logger block directly into your project. You own the code, you can debug it, and you can change it.
Why Blockend Logger Feels Different
- Shared logger instance across your app
- Automatic request ID propagation with
AsyncLocalStorage
- Framework adapters generated automatically (Express, Fastify, Hono)
- Request logging out of the box
- Built‑in redaction for sensitive fields
- Pretty logs in dev, JSON logs in prod
- TypeScript support baked in
Honest Comparison
| Feature | Blockend Logger | Traditional Pino |
|---|
| Setup | blockend-cli add logger | Manual install + config |
| Request IDs | Automatic | Manual middleware |
| Framework integration | Auto‑generated adapter | Write your own |
| Request logging | Built‑in | Add middleware manually |
| Redaction | Preconfigured | Manual setup |
| Output modes | Pretty dev / JSON prod | Configure transports yourself |
| TypeScript | Generated .ts files | Manual typings |
Blockend isn’t replacing Pino — it’s making Pino easier to use. If you want raw control, stick with Pino. If you want sane defaults and less boilerplate, Blockend Logger saves you time.
Learn More
Final Word
Logging should help you debug, not slow you down. Blockend Logger is basically “Pino with batteries included.” If you love it, star it on GitHub — that’s the best way to support the project and help more developers discover it.