create-evlog-framework-integration

This skill provides a systematic blueprint for extending the evlog observability framework to new HTTP frameworks, such as Hono, Elysia, Fastify, Express, or NestJS. It is designed for software engineers and maintainers aiming to unify their logging strategy by transforming fragmented console outputs into structured, request-scoped wide events. By following this 16-step integration process, you ensure that every new framework support package inherits the core benefits of evlog: automatic request tracing, structured error handling, performance telemetry, and seamless integration with ingestion pipelines.

• Implements the createMiddlewareLogger utility to handle the full request lifecycle, including enrichment, filtering, and asynchronous log draining.

• Standardizes framework-specific glue code for context injection, header parsing (supporting both Web API and Node.js formats), and error metadata attachment.

• Includes comprehensive build system updates in tsdown.config.ts and package.json to ensure correct ESM/CJS exports and peer dependency management.

• Provides a robust testing architecture utilizing standard helpers for spying on drain calls, asserting sensitive header filtration, and validating wide event schemas.

• Facilitates end-to-end documentation coverage, automatically updating landing pages, installation guides, feature tables, and framework-specific usage examples.

• The integration process is strictly defined by a 16-point checklist that requires manual verification of source code, build configs, docs, and example applications.

• All integrations must leverage the shared/middleware, shared/headers, and shared/storage utilities to prevent logic duplication and maintain consistent observability patterns.

• Expected inputs include a new directory under packages/evlog/src, updated documentation in apps/docs/content, and a new example app to demonstrate functionality in a real-world setting.

• Outputs consist of a production-ready framework adapter, semantic versioning changesets, and updated workflow templates (semantic-pull-request) to support automated CI/CD.

• The workflow enforces type safety through framework-specific module augmentation, ensuring that the useLogger() context is accessible and typed correctly within the framework's handler ecosystem.