Post

Hugo
@hugorcd.com

Spent the last few days making evlog easier to say yes to. Now you install it, you import it, it logs. Like pino, like consola. No setup, no config, no initLogger() before the first line. Wide events, drains, sampling, all of that is still there, you turn it on when you need it, not before.

Hugo
@hugorcd.com

Same thing for the CLI. Until now you had to install @𝖾𝗏𝗅𝗈𝗀/𝖼𝗅𝗂 on the side. Now it's just there: npx evlog map

Hugo
@hugorcd.com

Nothing to add to your package.json. The package grew by 1.6 kB, that's it. And map tells you exactly where your logging is missing, which is honestly worth the minute on its own. Already on OpenTelemetry? Nothing to learn, evlog reads the same env vars your OTel SDK already uses.

0 reposts0 likes

Hugo
@hugorcd.com

Lots of smaller things too: fatal and trace levels, wrapped errors that finally keep their cause, printf-style messages, evlog init that tells you which env vars you forgot. Full list in the reply. If you've been meaning to try it, this is the version to do it with. evlog.dev

evlog.devevlog — Digging through logs is not observability. It's hope.A modern TypeScript logger built for everything you ship — scripts, libraries, jobs, edge, requests. Simple logs, wide events, and structured errors in one API.