npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@headless-lms/adapter-db

v0.8.0

Published

Drizzle/Postgres persistence adapter for the headless LMS

Readme

@headless-lms/adapter-db

Drizzle/Postgres persistence adapter. Implements the outbound repository ports from @headless-lms/core and ships the migrations for the LMS database.

It depends on @headless-lms/core, drizzle-orm and pg — never on the server or any other adapter.

Layout

| Path | What lives there | | --------------------- | -------------------------------------------------------------------------- | | src/schema/ | Drizzle tables, grouped by owning context, barrelled in index.ts | | src/repositories/ | One Drizzle*Repository per context port, plus pg error translation | | src/client.ts | createDb — pool + drizzle instance; Db, Tx, DbExecutor types | | src/unit-of-work.ts | DrizzleUnitOfWork — transaction scope for the core UnitOfWork port | | src/migrate.ts | runMigrations(databaseUrl) against the packaged drizzle/ folder | | drizzle/ | Generated SQL migrations and snapshots (committed, shipped in the package) |

Usage

import { createDb, runMigrations, DrizzleProgressRepository } from "@headless-lms/adapter-db";

await runMigrations(process.env.DATABASE_URL!);

const db = createDb(process.env.DATABASE_URL!);
const progress = new DrizzleProgressRepository(db, logger);

Repositories take a DbExecutor, so the same class works against the root db or a transaction handle. DrizzleUnitOfWork builds a tx-bound scope, guaranteeing nothing escapes the transaction:

const uow = new DrizzleUnitOfWork(db, (tx) => ({
  progress: new DrizzleProgressRepository(tx),
  outbox: new DrizzleOutboxRepository(tx),
}));

await uow.run(async ({ progress, outbox }) => {
  /* ... */
});

Error translation

repositories/pg-errors.ts turns driver failures into domain errors — unique violations become ConflictError, everything else becomes a DbQueryError carrying the SQL text and structured pg fields but never the bind params (they can hold PII).

Drift checks

schema/drift.ts provides compile-time assertions that a table's row type matches its domain type from @headless-lms/core/schemas. A row field may be wider than the domain's, never narrower, missing, or extra. Drift fails pnpm typecheck with the offending keys.

Migration workflow

Push during dev, generate once at the end.

pnpm db:push       # apply schema changes straight to the dev database, no files
pnpm db:generate   # diff against the last committed snapshot → one migration
pnpm db:migrate    # apply pending migrations

While iterating locally, use db:push. When the schema is settled and ready to ship, run db:generate once — it diffs against the last committed snapshot, so you get a single migration containing everything since the previous release.

All three read DATABASE_URL from the repo-root .env.

Tests

pnpm test        # vitest
pnpm typecheck