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

effect-db

v0.19.0

Published

`effect-db` is the Postgres schema tooling package in this workspace. It ships the `effectdb` binary.

Readme

effect-db

effect-db is the Postgres schema tooling package in this workspace. It ships the effectdb binary.

Install

bun add effect-db

Config

Use effectdb.config.ts and import defineConfig from effect-db:

import { defineConfig } from "effect-db"

export default defineConfig({
  dialect: "postgres",
  db: {
    url: process.env.DATABASE_URL
  },
  source: {
    include: ["src/**/*.ts"]
  },
  migrations: {
    dir: "migrations",
    table: "effect_qb_migrations"
  },
  safety: {
    nonDestructiveDefault: true
  }
})

CLI

effectdb push
effectdb pull
effectdb migrate generate
effectdb migrate up

Operational Notes

effectdb manages canonical table and enum declarations, not the entire Postgres catalog.

Rollback

  • Use effectdb migrate down --steps N for recent migration files that were already applied.
  • If the change was generated with push, prefer restoring from backup before replaying migrations.
  • down only replays the migration history that effectdb knows about; it does not reconstruct data that was removed from the database.

Destructive Changes

  • Review effectdb push --dry-run output before applying schema changes.
  • Use --allow-destructive only when you have a backup or a separate recovery path.
  • Treat column drops, type changes, and table rewrites as manual operations when the resulting data loss matters.

Recovery

  • If migration bookkeeping gets out of sync, use effectdb migrate repair.
  • If the database schema drifted outside of migrations, reconcile the drift first, then regenerate or repair migration state.
  • After a bad deployment, restore the database, then bring the migration history back in sync before resuming normal deploys.

Unsupported Postgres Features

  • effectdb does not own views, triggers, stored procedures, functions, policies, grants, extensions, or other database-local objects.
  • Keep those objects in separate migrations or manage them outside the effectdb pull/push loop.
  • If you rely on server-side behavior that is not represented as table or enum declarations, do not expect pull to round-trip it.