nelo v0.2 alphaNelo gives TypeScript servers a clear lifetime for tasks, cancellation, resources, streaming, and shutdown.
Web Standards at the boundary. Explicit ownership underneath.
import { Nelo } from "nelo";
import { serve } from "nelo/node";
const app = new Nelo();
app.get("/report", async (c) => {
const report = c.fork(() => buildReport(c.signal));
return c.json(await report);
});
await serve(app, { port: 3000 }).listen();A handler can return while nested work, streams, and resources are still active. Nelo makes that boundary explicit instead of relying on developer discipline alone.
c.fork() binds work to the current request.The Node adapter connects Web Standards to real sockets, backpressure, client disconnects, and graceful shutdown without leaking Node-specific types into the portable root package.
The request scope records work as soon as it starts.
Nelo does not replace the platform. It keeps standard Request and Response objects while adding the ownership primitives that server applications are missing.
context.fork() creates eager, awaitable work that belongs to the request scope.
The first disconnect, error, or shutdown reason is preserved and propagated cooperatively.
context.use() releases resources once, in reverse acquisition order, even after failure.
The Node adapter reads response streams incrementally and waits for drain before continuing.
Stop accepting new requests, allow a grace window, then signal and close remaining sockets.
Application code works with Request, Response, Headers, ReadableStream, and AbortSignal.
The matrix reflects implemented and verified behavior, not aspirational compatibility.
Request → app.fetch() → ResponseStart with the portable Fetch API, then use nelo/node when transport-aware ownership is required.