--- title: "Framework Integrations" description: "Choose an evlog integration for Nuxt, Next.js, SvelteKit, Hono, Express, or another listed framework. Follow its setup and request-logger access guide." canonical_url: "https://www.evlog.dev/integrate/frameworks/overview" --- # Framework Integrations > Choose an evlog integration for Nuxt, Next.js, SvelteKit, Hono, Express, or another listed framework. Follow its setup and request-logger access guide. Choose your framework from the table below. `log.set()`, `createError()` and `parseError()` use the same core APIs, while initialization and request-logger access depend on the integration. Some stacks have a module or middleware, others need the manual setup shown in their guide. Every framework reads its options from one [`evlog.config.ts`](https://www.evlog.dev/reference/configuration). Nuxt, Nitro and TanStack Start load it for you; other frameworks import it. No HTTP framework? Use [Standalone TypeScript](https://www.evlog.dev/integrate/frameworks/standalone) for scripts, libraries, and workers, and [Cloudflare Workers](https://www.evlog.dev/integrate/frameworks/cloudflare-workers) on the edge. ## Pick your framework
Framework Import Type Logger Access Status
Nuxt evlog/nuxt Module useLogger(event) Stable
Next.js evlog/next Factory useLogger() Stable
SvelteKit evlog/sveltekit Hooks event.locals.log / useLogger() Stable
Nitro evlog/nitro Module useLogger(event) Stable
TanStack Start evlog/nitro/v3 Module useRequest().context.log Stable
TanStack Router evlog/nitro/v3 Module Via TanStack Start (uses Nitro v3) Stable
React Router evlog/react-router Middleware context.get(loggerContext) / useLogger() Stable
NestJS evlog/nestjs Module useLogger() Stable
Express evlog/express Middleware req.log / useLogger() Stable
Hono evlog/hono Middleware c.get('log') / useLogger() Stable
Fastify evlog/fastify Plugin request.log / useLogger() Stable
Elysia evlog/elysia Plugin log (context) / useLogger() Stable
oRPC evlog/orpc Handler wrapper + middleware context.log / useLogger() Stable
Effect evlog/effect Layer yield* EvlogLogger / yield* useLogger() Beta
Cloudflare Workers evlog/workers Factory createWorkersLogger() Stable
AWS Lambda evlog Manual createLogger() / createRequestLogger() Guide
Standalone evlog Manual createLogger() / createRequestLogger() Stable
Astro evlog Manual createRequestLogger() Guide
Custom evlog/toolkit Build your own createMiddlewareLogger() Beta
## What differs from one framework to the next Two things differ per framework: how you start evlog, and how a handler reaches the request logger. ### Start evlog
Pattern Frameworks
evlog(options) middleware / plugin Hono, Express, Fastify, Elysia, SvelteKit, React Router
createEvlog(options) factory Next.js
EvlogModule.forRoot() NestJS
routerLayer(options) layer Effect
Module default export Nuxt, Nitro v2/v3
Manual factory Cloudflare Workers ( createWorkersLogger ), Standalone, AWS Lambda, Astro
### Reach the logger from a handler
Pattern Frameworks
useLogger(event) Nuxt, Nitro
useLogger() Next.js, NestJS, Express, Fastify, Elysia, SvelteKit, React Router, Hono
c.get('log') Hono
req.log Express
request.log Fastify
event.locals.log SvelteKit
context.get(loggerContext) React Router
yield* EvlogLogger / yield* useLogger() Effect
createRequestLogger() / createLogger() Standalone, Workers, manual setups
On Hono, use `c.get('log')` inside handlers and `useLogger()` from `evlog/hono` in the layers underneath. See [Hono integration](https://www.evlog.dev/integrate/frameworks/hono). ## Full-stack frameworks Register `evlog/nuxt` in your modules to get auto-imported `useLogger`, `createError`, and `parseError`. `createEvlog()` factory with `withEvlog()` handler wrapper and client provider. Handle and handleError hooks with request-scoped logger on `event.locals.log`. Module for both Nitro v2 and v3 with plugin-based drain and enrichment hooks. Uses Nitro v3 module with async context, so `useLogger()` works inside server functions. Also covers TanStack Router (full-stack mode). Middleware with `context.get(loggerContext)` and `useLogger()` for loaders and services. `EvlogModule.forRoot()` with global middleware, exception filter, and async config. ## Server frameworks Middleware with `req.log` and 4-argument error handler. Middleware with typed `c.get('log')` via `EvlogVariables`. Plugin with `request.log` that shadows Fastify's built-in pino logger. Plugin with `log` in route context via Elysia's `derive`. Handler wrapper + procedure middleware exposing `context.log` and per-procedure `operation`. Beta. `routerLayer` for `HttpRouter` and `HttpApi`, `EvlogLogger` in the Effect context, and `withLogger` for jobs and alarms. Factory for creating request-scoped loggers with Cloudflare-specific context. `initLogger` once per runtime; `createLogger` per invocation (SQS, events, HTTP API). For scripts, CLI tools, queues, and any TypeScript process. Build your own middleware with the evlog toolkit API. All frameworks support the same features: [wide events](https://www.evlog.dev/learn/wide-events), [structured errors](https://www.evlog.dev/learn/structured-errors), [drain adapters](https://www.evlog.dev/integrate/adapters/overview), [enrichers](https://www.evlog.dev/use-cases/enrichers), [sampling](https://www.evlog.dev/learn/sampling), and [AI SDK integration](https://www.evlog.dev/use-cases/ai-sdk/overview). ## Strip client logs at build time For any Vite-based project, the [`evlog/vite` plugin](https://www.evlog.dev/reference/vite-plugin) adds build-time optimizations: - **Auto-initialization**: no `initLogger()` call needed - **Debug stripping**: `log.debug()` removed from production builds - **Source location**: inject `__source: 'file:line'` into log calls It works with SvelteKit, Hono through vite-node, and any Vite-powered setup. Under Nuxt the same three options live on the `evlog/nuxt` module, so the plugin does not need to be added by hand. ## Sitemap See the full [sitemap](https://www.evlog.dev/sitemap.md) for all pages.