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

dbtyper

v0.0.4

Published

Compile-time SQL parsing and schema typing for TypeScript.

Readme

dbtyper

Write plain SQL. Get fully typed rows. No ORM. No query builder DSL.

dbtyper is a compile-time SQL parser written in the TypeScript type system. It parses SQL string literals against a schema built from your migration chain and turns query results into TypeScript types.

const rows = await db.query(`
    SELECT id, display_name as name, email FROM auth.users
`)
// rows: Array<{ id: string; name: string; email: string }>

The SQL string stays the source of truth for which columns appear in the result. Rename a column in a migration and stale query/result usage becomes a TypeScript type error before you run the app.

Setup

Define your database through migrations:

import { sqlMigrations } from "dbtyper"
import type { PostgresDriver } from "dbtyper/postgres"

export async function exampleDb(driver: PostgresDriver) {
	return sqlMigrations({ driver })
		.apply((await import("../migrations/001.do.schemas.js")).generateSql())
		.apply((await import("../migrations/002.do.users.js")).generateSql())
		.apply((await import("../migrations/003.do.agenda.js")).generateSql())
		.database()
}

Connect with the Postgres adapter and query with plain SQL:

import postgres from "postgres"
import { postgresSqlDriver } from "dbtyper/postgres"

const db = await exampleDb(postgresSqlDriver({ sql: postgres(connectionString) }))

const rows = await db.query(`
    SELECT
        public.agenda.*,
        email,
        display_name
    FROM auth.users
    LEFT JOIN public.agenda
        ON auth.users.id = public.agenda.user_id
    ORDER BY email
`)

Why

The database boundary is usually a hole in TypeScript's type system. Migrations run, columns change, and string SQL only fails at runtime unless you have enough tests. With dbtyper, the schema lives in the type system, so migration changes propagate into query errors during the normal TypeScript feedback loop.

This keeps raw SQL readable while avoiding the usual abstraction stack around it: no ORM model layer, no query-builder DSL, no code generation step.

More

queryUntyped and streamUntyped are available for gradual adoption and SQL features the parser does not support yet.

Not production ready yet. It is still alpha.