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

@planetlogin/store-postgres

v0.2.0

Published

Batteries-included Postgres DownstreamStore for PlanetLogin — real accounts (password, OAuth, passkeys, TOTP, preferences) over any pg-compatible client, zero driver deps.

Readme

@planetlogin/store-postgres

A batteries-included DownstreamStore (spec §4) on Postgres — the same "0-to-login wedge" as @planetlogin/store-sqlite, for the database you probably already run in production.

Following core's RedisStore philosophy, it bundles no driver: you inject any pg-compatible client, so it works with pg, postgres.js (wrapped), Neon/serverless, or a Drizzle session. Zero npm runtime deps beyond the @planetlogin/core peer.

import { Pool } from 'pg';
import { postgresStore } from '@planetlogin/store-postgres';
import { passwordLogin, verifyPassword, signSession } from '@planetlogin/core';

const store = postgresStore(new Pool({ connectionString: process.env.DATABASE_URL }));
await store.ensureSchema();                    // idempotent — run once at boot

await store.createUser({ email: '[email protected]', password: 'hunter2' });

const result = await passwordLogin({ downstream: store, verifyPassword, signSession }, {
  identifier: '[email protected]',
  password: 'hunter2',
});
// → { ok: true, token, user }

The injected client

Any object with this shape works (that's pg's Pool/Client unchanged):

interface PgQueryable {
  query<R>(text: string, params?: unknown[]): Promise<{ rows: R[] }>;
}
  • pg / Neon: pass the Pool directly.
  • postgres.js: wrap it — { query: (t, p) => sql.unsafe(t, p).then((rows) => ({ rows })) }.
  • Drizzle: pass the underlying driver, or wrap db.execute.

Options

postgresStore(client, {
  tablePrefix,   // '' by default — e.g. 'pl_' to namespace inside a shared DB
  deliverMagic,  // (data) => void | Promise<void> — send the magic link (email/SMS).
                 // Omitted → logged to the console (dev) and recorded in magic_log.
});

API

Everything in core's DownstreamStore — findUser, upsertUser, deliverMagic, passkeysFind/Save, totpGet/Save, preferencesGet/Save — plus:

| Helper | Purpose | | --- | --- | | ensureSchema() | Create the tables if missing (idempotent). Run once at boot. | | createUser({ email, password?, passwordHash?, name?, locale?, id? }) | Create an account. password is hashed with argon2id. A duplicate email raises DownstreamConflictError — which self-serve sign-up turns into a 409. | | setPassword(identifier, password) | Replace a user's password (argon2id). | | deleteUser(identifier) | Remove a user and their passkeys/TOTP/preferences. |

Schema

ensureSchema() creates users, passkeys, totp, magic_log, preferences (prefixed by tablePrefix). locale and preference data are stored as JSONB. Emails are stored and matched lower-cased.

When to use what

  • Anonymous only (0 backend): the globe mints a signed locale token, no store.
  • @planetlogin/store-sqlite: real accounts in one file — the quickest start.
  • @planetlogin/store-postgres (this): real accounts on your production Postgres.
  • defineStore({...}): a store shape core doesn't ship — implement the contract.
  • HTTP Downstream: identity lives in a separate service (multi-service auth).