Browse documentation

Packages

On this page

Choose a package to see how to set it up, try an example, and use it in your project.

Foundation and tools

  • @dads-framework/dev Local development slots and conservative Git worktree lifecycle.
  • @dads-framework/plugin The build-time plugin contract: definePlugin declares what a plugin contributes and depends on, composeApp orders and checks a plugin list and returns what the host wires, and every effect a plugin starts is disposed with its scope.
  • @dads-framework/toolbox Explains Dads ownership and runs deterministic agent workflows.
  • create-dads Guides new and existing applications through deterministic Dads initialization.

Contracts and access

  • @dads-framework/access The TypeScript authoring kit for relationship-based authorization: access(), entity handles, combinators, and the emitter that writes committed generated/*.zed fragments. SpiceDB schema is generated from these definitions.
  • @dads-framework/contract HTTP-kit wire vocabulary every surface shares: the request-id header name,

Server

  • @dads-framework/audit Assembles row-level audit, request retention, and client diagnostics with the HTTP, jobs, and Postgres packages. Applications configure the tables, exclusions, and scope dimensions captured by the audit trigger.
  • @dads-framework/audit-actor Who is acting, in one dependency-free place: the AuditActor vocabulary, the exact JSON the Postgres dads.audit_actor setting carries, and the AsyncLocalStorage context that carries it. It lives apart from @dads-framework/audit because the postgres kit (attributed pool), the http kit (request scope), and the job-queue kit (system actor per job) all need the actor and none of them may depend on the audit kit to get it. Read the rest when: establishing an actor context at a new seam, or asking how an actor reaches the database.
  • @dads-framework/authorization SpiceDB checks and snapshots, Postgres outbox and catalog.
  • @dads-framework/authorization-migration The authorization schema journal: ordered NNNN_slug schema snapshots with the relationship steps that keep access intact, applied once each, plus the patch-form authorization changes and their scaffolding.
  • @dads-framework/cross-domain-references Builds reconciliation queries and reports dangling references using the database client supplied by the application.
  • @dads-framework/csv Encodes rows as CSV using RFC-style field quoting and LF line endings.
  • @dads-framework/email-delivery Binds the Postgres adapter to the durable email outbox and composes the delivery and sweep jobs over it.
  • @dads-framework/email-sender Send outbound email. Callers hold one EmailSender and call send(); the
  • @dads-framework/email-templates Turns a declarative email template into the HTML and plain-text pair a message
  • @dads-framework/errors DomainError (discriminated kind + stable SCREAMING_SNAKE code) with
  • @dads-framework/event-bus The EventBus seam for asynchronous cross-domain communication: domains
  • @dads-framework/feature-flags Defines feature flags, per-tenant audiences, revision-checked changes, and effective access. Its HTTP and PostgreSQL bindings expose and persist flag state.
  • @dads-framework/http Defines HTTP routes and assembles liveness and readiness probes over application-provided checks.
  • @dads-framework/identity Owns vendor-neutral account, session, and email delivery contracts.
  • @dads-framework/identity-better-auth Binds identity HTTP requests to Better Auth, PostgreSQL sessions, and account invitations.
  • @dads-framework/job-queue JobQueue: register typed definitions, start recurring schedules, enqueue
  • @dads-framework/migrations The Postgres migration runner: discovers *.migration.ts files in the folders a MigrationWorkspace names, applies pending ones in dependency order under an advisory lock, and journals and checksums what ran. Also ships the dads-migrate bins and the compatibility rehearsal.
  • @dads-framework/object-storage Put, get, delete, and sign download or single-PUT upload URLs for object bytes. The composition
  • @dads-framework/pdf PdfRenderer turns a declarative pdfmake definition into bytes. No Chrome.
  • @dads-framework/postgres Owns the Postgres pool and the Drizzle instance (createPostgresConnection),
  • @dads-framework/postgres-access Postgres backend for the composed access model and transactional relationship facts. Status: Trusted experimental.
  • @dads-framework/runtime Provides the clock, request work accounting, and diagnostic sinks used across server kits.
  • @dads-framework/telemetry Opt-in OpenTelemetry trace export for Node HTTP and Postgres.
  • @dads-framework/tenants Tenant lifecycle, membership authorization, and verified-account invitations.

Client

Web

Testing

  • @dads-framework/path-aliases Resolves the TypeScript path aliases declared across one tsconfig extends chain to files, over a file system port two providers implement.
  • @dads-framework/testing Bootstraps, plans, runs, and explains declared verification tasks through a native JSON boundary. Its Nx adapter imports recipes and adapts live targets.
  • @dads-framework/testing-vitest Binds the Dads alias resolver to Vite and Vitest as a pre-resolution plugin, without an Nx runtime dependency.

Native testing runtimes