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

@better-forge/db

v0.2.0

Published

SQLite (node:sqlite) and Drizzle bootstrap, transactions, schema and migration registries.

Readme

@better-forge/db

SQLite (node:sqlite) and Drizzle bootstrap, transactions, and the registries that let each module own its tables and migrations. No state of its own: the application opens the connection and passes it in.

import { composeModules, openDatabase, runMigrations, type DbModule } from '@better-forge/db'

const notes: DbModule = {
  id: 'notes',
  tables: { notesTable },               // Drizzle tables the module owns
  migrations: [
    { kind: 'exec', sql: 'CREATE TABLE IF NOT EXISTS notes (...)' },                       // idempotent DDL
    { kind: 'column', sql: 'ALTER TABLE notes ADD COLUMN pinned INTEGER', desc: 'notes.pinned' }, // tolerates "already applied" only
    { kind: 'data', name: 'seed-notes-v1', run: (sqlite) => { /* once, in a transaction */ } },
  ],
}

const { schema } = composeModules([auth, audit, notes])   // throws on a repeated module, table export or data name
const { sqlite, db, close } = openDatabase({ path, schema })
runMigrations(sqlite, [auth, audit, notes])               // modules run in the order given

Rules for a module's migrations:

  • Steps run in the listed order on every start, so each must be idempotent.
  • A data step's name is stored in schema_migrations. Never rename or drop one: it would run again on existing data.
  • Order matters where SQLite stores the statement text: columns added with ALTER keep their relative order per table.
  • A module may rely on the tables of the modules listed before it.

drizzle-orm is a peer dependency, so the application and every module share one copy. Requires Node 22.5 or newer.

Status: pre-1.0.