review-logging-patterns

To fix console.log spam and unstructured errors, run a code review that detects scattered logs and guides you to consolidate them into structured wide events using evlog. This enforces best practices for structured errors, request context, and drain pipelines.

Wide events in structured logging combine scattered console logs into a single, context-rich event record. You need them when debugging requires correlating request context, enrichers, and structured errors across frameworks like Nuxt, Next.js, or Express.

Yes, evlog works with Nuxt/Nitro, Next.js, SvelteKit, TanStack Start, React Router, NestJS, Express, Hono, Fastify, Elysia, Cloudflare Workers, and standalone TypeScript, providing framework-specific error handling and logging templates.

The best way to adopt wide event logging in NestJS or Fastify is to run a framework audit that identifies logging anti-patterns, then apply evlog templates for structured errors, drain pipelines, and enrichers specific to your framework.

You configure drain pipelines and enrichers by adopting evlog patterns that enforce best practices for structured errors. The Skill provides references and templates to guide this setup across supported frameworks.