review-logging-patterns

Replace console.log spam with structured logging by using evlog's log.set() to accumulate request and business context, then emitting a single wide event per request or job. This eliminates scattered logs and improves debugging visibility.

Create structured errors using the createError() payload, which replaces generic throw Error() patterns with self-documenting fields including message, why, fix, optional link, and preserved cause for clearer root cause analysis.

Set up a production-grade logging drain pipeline by configuring batching, retry, and overflow safeguards, along with enrichment, sampling, and route service mapping tailored to frameworks like Next.js, Hono, Fastify, and Cloudflare Workers.

Yes, evlog structured logging works with Nuxt, NestJS, SvelteKit, and many other frameworks including Express, Elysia, and TanStack Start, providing specific setup and usage patterns for request handlers and background jobs.

Detect logging anti-patterns during code reviews by applying YAML-discoverable guidance that checks for scattered console usage and generic error throws, enforcing contextual log.set() accumulation and structured createError() payloads.

Use wide events instead of standard console logging when you need to consolidate scattered context into a single structured event per request or job, improving incident response and debugging across TypeScript/JavaScript backends.