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 point | Contents |
|---|---|
@senrijs/senri | The app, routes, Context, errors, validation and the built-in middleware |
@senrijs/senri/dev | Development mode |
@senrijs/senri/cookie | Reading, setting and deleting cookies. Signed cookies |
@senrijs/senri/ip | The client IP |
@senrijs/senri/streaming | Sending a response bit by bit. Server-Sent Events |
@senrijs/senri/multipart | Reading large uploads without buffering them in memory |
@senrijs/senri/problem | RFC 9457 Problem Details |
@senrijs/senri/jwt | Signing and verifying JWTs |
@senrijs/senri/client | A typed client made from the type of a route table |
@senrijs/senri/testing | Calling an app without a server |
@senrijs/senri/websocket | WebSocket routes |
@senrijs/senri/openapi | Making an OpenAPI document from a route table |
@senrijs/senri/otel | OpenTelemetry traces |
@senrijs/senri/metrics | Prometheus metrics |
@senrijs/senri/node | Running on node:http on Node.js |
@senrijs/senri/serve | Starting the app on the detected runtime |
@senrijs/senri/static | Static files |
@senrijs/senri/context-storage | Getting c from anywhere |
The type tables are generated from the source types and their JSDoc.