review-logging-patterns

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: Client ingest endpoint — receives client logs: Access the logger via event.locals.log in route handlers or useLogger() from anywhere in the call stack: Full pipeline with drain, enrich, and tail sampling: TanStack Start uses Nitro v3. Install evlog and add a nitro.config.ts : Add the error handling middleware to __root.tsx : Use useRequest() from nitro/context to access the logger: Import useLogger from evlog/nitro in routes. EvlogModule.forRoot() registers a global middleware. Use useLogger() to access the request-scoped logger from any controller or...