review-logging-patterns

Structured logging for TypeScript/JavaScript with framework-agnostic setup, wide events, and drain adapters. Review and improve logging patterns in TypeScript/JavaScript codebases. Transform scattered console.logs into structured wide events and convert generic errors into self-documenting structured errors. All evlog functions ( useLogger , createError , parseError , log ) are auto-imported — no import statements needed. Drain, enrich, and tail sampling use Nitro hooks in server plugins: Client transport (auto-configured Vue plugin): Client-side: log , setIdentity , clearIdentity are auto-imported in components. Step 1: Create central config — all exports come from here: Step 2: Wrap route handlers with withEvlog() : Step 3: Server Actions — same withEvlog() wrapper: Step 4: Middleware (optional — sets x-request-id + timing headers): Step 5: Client Provider — wrap root layout: Step 6: Client logging — in any client component: Step 7 (optional): Instrumentation — startup + global onRequestError (SSR/RSC errors outside withEvlog ). Use defineNodeInstrumentation(() => import('./lib/evlog')) in root instrumentation.ts to gate Node + cache the import, or write register / onRequestError manually — both are valid. For custom logic, wrap evlog’s register / onRequestError inside lib/evlog.ts (compose with your own init or metrics), then re-export.