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

@tegmentum/datalink-browser

v0.5.0

Published

DB-agnostic browser runtime plumbing for datalink (DuckDB / SQLite wasm components): WASI polyfill configuration, jco component instantiation (JSPI fast-path + non-JSPI Web Worker fallback over postMessage RPC), and the extension-host registration bridge.

Readme

@tegmentum/datalink-browser

DB-agnostic browser runtime plumbing for datalink SQL-engine wasm components (DuckDB, SQLite). This is Tier 3 of the datalink consolidation (CONSOLIDATION.md): the plumbing shared by every engine facade, lifted from the ducklink web/ harnesses and the sqlink browser/src runtime.

What's here

| Module | From | Role | | --- | --- | --- | | polyfill.mjs | ducklink run-core.mjs configurePolyfill | the WASI plugin set (cli/io/fs/clocks/random/sockets) on @tegmentum/wasi-polyfill + an in-memory FS policy; engine-specific mkdirs / ws-gateway are options | | runtime.mjs | ducklink run-core.mjs instantiateCore | jco transpile via createRuntimeBindgen + JSPI config (jspiAvailable feature-detect) | | extension-host.mjs | ducklink extension-host.mjs | preload + coreImports + callback dispatch, generalized to a multi-extension router (per-extension handle namespace) | | resolver.mjs | new (over registry/index.json) | the conformance gate (passed && at === wit_contract) + content-digest verify + provider precedence | | fetch-bytes.mjs | new | fetchBytes / sha256Hex helpers |

These are engine-agnostic: the DuckDB-specific value/type marshalling, the TVM spill host, and the exact JSPI import/export lists live in the engine facade (@tegmentum/ducklink) and are passed in as options. SQLite gets the same plumbing for free (@tegmentum/sqlink).

Status

Built + proven via the @tegmentum/ducklink facade in headless Chromium. Worker harness and the full Tier-3 polish (lifting sqlink's runtime onto this too) are follow-ons.