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

@potluckdb/potluckdb-browser

v0.1.0

Published

potluckdb browser application SDK and WASM runtime

Readme

potluckdb for the browser

potluckdb ships for the browser as one release target: the runtime compiled to WebAssembly, packaged with the worker that hosts it and the application API of the Node package. Databases live in the origin's private file system; a remote is a directory there or a bucket reached from the page.

Installation

npm install @potluckdb/potluckdb-browser

The package is an ES module. The server, in development and in production, sends Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp with the page.

Usage

import { open, storage } from "@potluckdb/potluckdb-browser";

const credentials = async () => {
  const response = await fetch("/api/storage-credentials");
  return response.json(); // { accessKeyId, secretAccessKey, sessionToken, expiresAt }
};
const remote = await storage.fromS3({ bucket: "my-bucket", namespace: "notes", region: "eu-west-1", credentials });
const db = await open("app", remote);

The trial and the license key apply. A page has neither an environment nor a configuration directory, so the license key is passed as the licenseKey open option, and the trial's anchor is kept in the origin private file system beside the databases.

The browser page gives the headers a page needs, buckets from a page, and the quickstart.

See LICENSE.