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

@jswob/drizzle-utils

v0.1.1

Published

Runtime helpers for Drizzle and PostgreSQL: database targets, SSL, prepared statements, error codes

Readme

@jswob/drizzle-utils

Runtime helpers for Drizzle ORM on postgres.js: database targets, the SSL choice, prepared statements, a many-row CASE, PostgreSQL error codes and a query counter for tests.

bun add @jswob/drizzle-utils drizzle-orm postgres

It ships TypeScript source: import it from Bun, Vite or Vitest.

Exports

| Export | What it is | | --------------------------------------------------------------- | --------------------------------------------------------------------------------- | | createDbTargets(defaultNames) | dbTarget and selectedDbTarget for the app, test and e2e databases | | databaseSsl(url) | require or false: DATABASE_SSL when set, else the URL's sslmode=require | | withPreparedStatements(client) | Wraps a postgres.js client so every query Drizzle sends is a prepared statement | | caseBy(key, column, pairs) | A CASE giving each row its own value, for a many-row update in one statement | | isPgError(error, code) | Whether a thrown error carries a SQLSTATE code, on itself or on Drizzle's cause | | isUniqueViolation, isCheckViolation, isExclusionViolation | isPgError for 23505, 23514, 23P01 | | dbNow() | now(), for a timestamp written on update by the database's clock | | createQueryCounter() | debug for a postgres.js client and countQueries(run), for query-budget tests |

Database targets

import { createDbTargets } from '@jswob/drizzle-utils';

export const { dbTarget, selectedDbTarget } = createDbTargets({
	app: 'app_db',
	test: 'app_test_db',
	e2e: 'app_e2e_db',
});

const { url } = dbTarget('test');

It reads DB_HOST, DB_USER, DB_PASSWORD, then DB_NAME/DB_PORT, TEST_DB_NAME/TEST_DB_PORT and E2E_DB_NAME/E2E_DB_PORT (ports 5432, 5433 and 5434 when unset). app is DATABASE_URL when it is set; test and e2e never are, so a test can never reach production.

License

MIT