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

@openknot-ts/postgres-client

v0.0.6-preview

Published

PostgreSQL pool resource and health check for OpenKnot applications, over node-postgres.

Readme

@openknot-ts/postgres-client

Manages an application-created node-postgres pg.Pool as a Wire resource, with a health check.

Usage

import { postgresClient, postgresHealthCheck } from "@openknot-ts/postgres-client";
import { config } from "@openknot-ts/wire";
import pg from "pg";

const settings = config({ DATABASE_URL: z.string().url() });

export const postgres = postgresClient({
  requirements: { settings },
  create: ({ settings }) =>
    new pg.Pool({ connectionString: settings.DATABASE_URL, connectionTimeoutMillis: 5_000 }).on("error", report),
});

export const transaction = unit({
  requirements: { postgres },
  factory: ({ postgres }) => drizzleUnitOfWork({ database: drizzle({ client: postgres }) }),
});

export const io = providePlugs([postgres, postgresHealthCheck({ postgres }), transaction /* readers, writers */]);

API

| Export | Description | | --- | --- | | postgresClient({ requirements?, create }) | The pool as a resource. Resolves to the native pool, for direct use or Drizzle (drizzle-uow, @openknot-ts/drizzle-outbox/pg). | | postgresHealthCheck({ postgres, name?, timeoutMs? }) | SELECT 1 within the check's deadline (one second by default). |

Lifecycle

  • create chooses the pool's settings. Attach an error listener there: an unhandled idle-client error ends the process.
  • Acquisition checks out one connection, so an unreachable server or bad credentials fail startup.
  • A failed or cancelled startup ends the pool. node-postgres cannot cancel a connection attempt, so set connectionTimeoutMillis to bound every attempt.
  • Release ends the pool once and completes only when every connection has closed its socket.

Tests

test/client.test.ts covers refused and cancelled startups. test/postgres.integration.ts runs against a real server:

DATABASE_URL=postgres://user:password@localhost:5432/db pnpm --filter @openknot-ts/postgres-client test:postgres