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

@broberg/db-sdk

v0.1.0

Published

Thin shared database client for the WebHouse fleet — one DB SDK, every project. Turso/libSQL today; Postgres/Supabase transports later. Pilot: Buddy Cloud (F067).

Readme

@broberg/db-sdk

The WebHouse fleet's shared database transport — one thin facade every project depends on, instead of scattering driver calls across repos. The same play as @broberg/ai-sdk, for the data layer.

Turso/libSQL today; Postgres/Supabase transports planned behind the same API. Pilot consumer: Buddy Cloud (F067).

Install

bun add @broberg/db-sdk
# or: npm i @broberg/db-sdk

Use

import { createClient, createReplica, health } from '@broberg/db-sdk';

// Remote (cloud hub). Reads TURSO_DATABASE_URL + TURSO_AUTH_TOKEN from env.
const db = createClient();
await health(db); // { ok: true, version: "3.45.1" }

// Embedded replica (edge daemon): a local file synced from the remote primary.
const edge = createReplica({ path: '/data/buddy.db', syncIntervalSeconds: 30 });
// reads hit the local file at SQLite speed; writes forward to the primary
await edge.sync(); // or rely on the interval

Thin by design. No ORM coupling — layer Drizzle in the consumer:

import { drizzle } from 'drizzle-orm/libsql';
import { createClient } from '@broberg/db-sdk';
const orm = drizzle(createClient(), { schema });

API

| Export | Signature | What it does | |---|---|---| | createClient | (cfg?: DbConfig) => Client | Remote client. cfg: { url?, authToken?, backend? } (env fallback). | | createReplica | (cfg: ReplicaConfig) => Client | Embedded replica. cfg: { path, syncUrl?, authToken?, syncIntervalSeconds?, backend? }. | | health | (client) => Promise<{ ok, version }> | Liveness + SQLite-version probe. |

Re-exports Client / ResultSet (from @libsql/client) and the config types.

Multi-backend roadmap

backend defaults to 'libsql' (Turso) — the only transport implemented today. postgres / supabase are the planned extension points: a new transport lands under src/backends/ and widens the Backend union, without changing the public createClient / createReplica surface. The domain layer (ORM, schema, tenant-scoping) stays in each consumer.

License

FSL-1.1-Apache-2.0 © Christian Broberg