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

@karpo.dev/sdk-web

v0.4.0

Published

Karpo client for browsers: SQLite in a worker, OPFS persistence, live queries.

Downloads

531

Readme

@karpo.dev/sdk-web

The Karpo client for browsers. It runs the SDK core and SQLite WASM in a dedicated worker, persists the replica to OPFS, and keeps queries live: reads hit local SQLite, writes land locally first and sync in the background.

npm install @karpo.dev/sdk-web

Usage

import { createKarpoClient } from "@karpo.dev/sdk-web";
import schema from "./karpo/generated/schema.json";

const karpo = await createKarpoClient({
  schema,
  user: "u01",
  target: "dev",          // or gatewayUrl for a backend the SDK has no name for
  publishableKey: "pk_…", // engages the auth surface
});

// One read-only statement; anything that is not a single SELECT is rejected.
const rows = await karpo.runtime.selectSql("select * from todos order by title", []);

await karpo.runtime.insert("workspaces", "todos", {
  containerId: "ws-demo",
  title: "Write the README",
});

Most apps do not call this directly — karpo generate emits a karpo.ts that wraps it as initKarpo() and exposes a typed db.

What the package handles for you

  • Multi-tab. By default one tab is elected leader and owns the replica, the poke socket, and the token-refresh timer; the others route their SQL to it and are promoted when it goes away. That is what makes the device identity a property of the browser profile rather than of the window. multiTab: "per-tab" gives every tab its own device and replica.
  • Fallback. Where a worker or OPFS is unavailable the same core runs on the main thread over sqlite-wasm's localStorage VFS. Behavior is identical; persistence is not, so the fallback is logged at error level.
  • The inspector. In a dev build the devtools agent is installed automatically, and @karpo.dev/devtools serves the UI at /__karpo.

Vite must not pre-bundle the workers, or new URL("./worker.js", import.meta.url) resolves next to the bundle instead of next to the package:

optimizeDeps: { exclude: ["@sqlite.org/sqlite-wasm", "@karpo.dev/sdk-web"] }

Without it the app still runs — it quietly falls back to the main thread and loses OPFS persistence, which is a bad thing to discover later.

Docs: https://karpo.dev/web and https://karpo.dev/database. Source: https://github.com/Chirich-GmbH/karpo-core (packages/sdk-web).