Documentation
errorcore is built for one job: make production failures easier to explain. The docs stay close to that job. Each section focuses on a narrow capability, the expected behavior, and the smallest example that proves the feature is working.
Start with setup, then move into capture, transport, and policy. Use the reference pages when you need exact option names or type shapes.
Sections
Getting Started
Install the SDK, initialize it early, and confirm a first captured failure.
Capturing Errors
Choose between automatic capture, manual reporting, request context, and local state.
Middleware
Wire the SDK into Express, Fastify, Koa, Hapi, or a raw HTTP server.
IO Recording
Understand how outbound HTTP, database queries, and DNS events are recorded.
Database Support
Review the expectations for PostgreSQL, MySQL, MongoDB, and Redis capture.
State Tracking
See how runtime state is organized once an incident is captured.
Security
Control encryption and scrubbing before incident packages leave the process.
Transport
Pick delivery targets and dead-letter behavior for your environment.
CLI
Create config, validate setup, inspect status, and drain stored packages.
Error Handling
Handle SDK backpressure, capture failures, and package-level failure modes.
Reference
Look up option names and TypeScript-facing API details.