@dads-framework/runtime
On this page
Provides injectable clocks, request work accounting, and server fault reporting.
Try it
In a Node.js 22+ project, install the package.
Shell
npm install @dads-framework/runtime
Save this as example.mts and run node --experimental-strip-types example.mts.
TypeScript
import { type Clock } from "@dads-framework/runtime/clock";
function dueAt(clock: Clock, delayMs: number) {
return new Date(clock.now().getTime() + delayMs);
}
const fixed = { now: () => new Date("2026-01-01T00:00:00Z") };
console.log(dueAt(fixed, 60_000).toISOString());
The script prints 2026-01-01T00:01:00.000Z.
Use it
| Import | Use |
|---|---|
@dads-framework/runtime/clock |
Inject a Clock so callers can supply system or fixed time. This entry point works in browsers. Clock examples |
@dads-framework/runtime/request-work |
Start a request tally and charge database queries and authorization checks. Request work examples |
@dads-framework/runtime/request-work/testing |
Start a tally around a test callback with measureRequestWork. |
@dads-framework/runtime/diagnostics |
Capture exceptions with a consistent fingerprint using createDiagnosticsReporter. Diagnostics examples |
@dads-framework/runtime/diagnostics/testing |
Record captured exceptions with FakeDiagnosticsReporter. |
Request work and diagnostics use Node.js APIs.
What it refuses to do
Request work tracks the cost of calls inside the current request. The HTTP app owns request deadlines and shutdown. Diagnostics sends a fingerprint and selected exception details. Application composition owns reporter configuration and shutdown.
Contract
Clock.now()returns aDate. Use a monotonic clock for elapsed time.- Request work charges successful and failed calls and leaves each call's result or error intact.
DiagnosticsReporter.captureException()returnsvoidand never throws. Callflush(timeoutMs)to wait for buffered reports andclose()during shutdown.