# HugoRCD/evlog

Digging through logs is not observability. It's hope — wide events, structured errors, TypeScript-first, every runtime.

Repository: https://github.com/HugoRCD/evlog
Canonical: https://ross.abutalabs.com/products/evlog
Homepage: https://evlog.dev
Language: TypeScript
License: MIT
License Family: permissive
Topics: debugging, error-handling, logging, nuxt, observability, typescript, wide-events, otlp, posthog, sentry, nextjs, logger
Last push: 2026-08-26T17:30:00+00:00

## Health v2 (maintenance only)
Score: 82/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 99, longevity 15
- inputs: {"age_days": 221, "days_push": 7, "days_rel": 7, "gap_med": 2.0, "n_releases_24m": 59}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1815, forks 60 (observed 2026-08-28T04:05:39.777471+00:00)

## What it is
evlog is a modern TypeScript logging library that combines structured logs, wide events, and structured errors behind a single API and drain pipeline. It ships integrations for every major TypeScript server framework (Nuxt, Next.js, SvelteKit, Express, Hono, Fastify, NestJS, Cloudflare Workers, and more) and is designed to be machine-readable for AI agents.

## Use cases
- replace console.log or pino with structured logging in a TypeScript app
- emit one wide event per request with full accumulated context
- throw structured errors that explain why they happened and how to fix them
- add request logging middleware to Express, Hono, Fastify, or NestJS
- write NDJSON logs locally so AI coding agents can diagnose failures
- ship logs to observability backends like Sentry, PostHog, Datadog, or OTLP endpoints
- score which API entry points lack observability with evlog map

## When to choose
- you want wide events and structured errors instead of scattered log lines
- you need one logger API across many TypeScript frameworks and runtimes including edge workers
- you want a lightweight, zero-dependency logger (~6 kB gzip)
- you want logs that AI agents can parse and act on

## When to avoid
- you are locked into a non-TypeScript/JavaScript stack
- you need a battle-tested incumbent like pino or winston with a large ecosystem
- you only need trivial console logging with no structure

## Facets
- artifact type: library
- maturity: active
- function: logging, error-handling, monitoring, developer-tools
- domain: developer-tools, backend, web-development, monitoring
- platform: cross-platform, cli
- tags: wide-events, structured-logging, structured-errors, typescript, nuxt, nextjs, otlp, sentry, posthog, drain-pipeline, ai-agent-friendly, nodejs, web-server

## Member repositories
- HugoRCD/evlog (main) score 82

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:39.777471+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:20:37.318522+00:00, confidence not recorded.
  - readme: https://github.com/HugoRCD/evlog (fetched 2026-08-28T04:05:39.777471+00:00, sha d9ace34fd088)
  - homepage: https://evlog.dev (fetched 2026-08-29T10:59:40.036003+00:00, sha 4215ad9d67ea)
  - site_page: https://www.evlog.dev/start/installation (fetched 2026-08-29T10:59:40.047478+00:00, sha 16c15789910d)
  - registry_npm: https://registry.npmjs.org/evlog (fetched 2026-08-29T10:59:40.050842+00:00, sha 2d21edb5d83d)
  - site_page: https://www.evlog.dev/start/introduction (fetched 2026-08-29T10:59:40.045508+00:00, sha 3b7522bd2c1b)
  - site_page: https://www.evlog.dev/integrate/frameworks/overview (fetched 2026-08-29T10:59:40.049125+00:00, sha ec54d74758e5)
- Data as of 2026-08-30T08:39:29.467469+00:00.
