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

@work.books/substrate

v0.1.0

Published

Workbook substrate v0 — file-as-database persistence (parser, hydrator, integrity guard)

Readme

@work.books/substrate

Workbook substrate v0 — file-as-database persistence for workbook HTML files.

Goal

A workbook is a single .workbook.html file that is the database. State (yjs CRDT bytes for the spec/composition, optionally SQLite bytes for relational data) lives inline in the file. Edits are persisted by writing the file back to disk through the strongest transport available on the user's browser/OS.

File model (v0)

<!DOCTYPE html>
<html>
<head>
  <meta name="workbook-substrate" content="v0">

  <script type="application/json" id="wb-meta">
    {"workbook_id": "uuid", "schema": 0, "runtime_version": "0.1.0"}
  </script>

  <!-- Cold image. Compacted periodically. One per data container. -->
  <script type="application/octet-stream"
          id="wb-snapshot:composition"
          data-cid="bafy…"
          data-format="yjs">base64…</script>

  <script type="application/octet-stream"
          id="wb-snapshot:data"
          data-cid="bafy…"
          data-format="sqlite">base64…</script>

  <!-- Hot log. Append-only at the format level; physical writes
       depend on the transport. -->
  <script type="application/json" id="wb-wal">
  [
    {"seq": 1, "target": "composition", "parent_cid": "bafy…",
     "cid": "bafy…", "payload_b64": "…"},
    {"seq": 2, "target": "data", "parent_cid": "bafy…",
     "cid": "bafy…", "payload_b64": "…"}
  ]
  </script>

  <script type="module" id="workbook-runtime">…</script>
</head>
<body>
  <div id="app"></div>
</body>
</html>

All persisted bytes live inside <script type="application/octet-stream"> or <script type="application/json"> data blocks — parser-inert, content preserved verbatim, retrievable via document.getElementById(id).textContent or via fetch(self.location).then(r => r.text()) for binary-safe extraction.

Status

In development. See spikes/ for in-progress feasibility studies and bd show core-1ja for the project plan.