Skip to Content
Senri
API reference

Entry points

The entry points of @senrijs/senri and what each one has

Senri splits its features into entry points. Code from entry points you do not use is not bundled. The entry points are the same on npm and JSR.

Entry pointContents
@senrijs/senriThe app, routes, Context, errors, validation and the built-in middleware
@senrijs/senri/devDevelopment mode
@senrijs/senri/cookieReading, setting and deleting cookies. Signed cookies
@senrijs/senri/ipThe client IP
@senrijs/senri/streamingSending a response bit by bit. Server-Sent Events
@senrijs/senri/multipartReading large uploads without buffering them in memory
@senrijs/senri/problemRFC 9457 Problem Details
@senrijs/senri/jwtSigning and verifying JWTs
@senrijs/senri/clientA typed client made from the type of a route table
@senrijs/senri/testingCalling an app without a server
@senrijs/senri/websocketWebSocket routes
@senrijs/senri/openapiMaking an OpenAPI document from a route table
@senrijs/senri/otelOpenTelemetry traces
@senrijs/senri/metricsPrometheus metrics
@senrijs/senri/nodeRunning on node:http on Node.js
@senrijs/senri/serveStarting the app on the detected runtime
@senrijs/senri/staticStatic files
@senrijs/senri/context-storageGetting c from anywhere

The type tables are generated from the source types and their JSDoc.