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

@voidbase-cloud/plugin-previews

v0.9.0-beta.60

Published

The previews plugin of voidbase: a preview per pull request, as its own instance or as a marked lane on this one

Readme

@voidbase-cloud/plugin-previews

The previews plugin of voidbase, as a package of its own. It is what an instance knows about being a preview: which of the two shapes it is in, which branches have rows on it, and the route that takes a branch's rows away again.

It ships with voidbase and is on by default — @voidbase-cloud/voidbase depends on this package and loads it — so an instance needs nothing here. Install it yourself only to load it into an app that builds its own plugin graph.

The shape

A preview comes in two shapes, and only one of them makes an instance.

  • --shape instance is a Worker of its own, with its own database, bucket and queue, deployed for one branch and seeded from production. Everything about making one happens around a deploy, in the plugin's deploy-time half — which is not in this package: a deploy plugin runs inside voidbase deploy, in the CLI's process, against the Cloudflare and GitHub APIs, so src/node/plugins/previews.ts stays in the core and reads the two var names and the naming rule back through @voidbase-cloud/voidbase/plugins/previews, the entry the core keeps.
  • --shape flagged makes no instance at all: the branch shares production and its writes carry a mark that production's reads filter out. The mark and the filter are in the core's records path, because every read has to agree about them; /records-preview publishes the four names a plugin needs of it, and /records-files the one call that empties a deleted row's files.

The first extracted plugin with routes of its own — GET /api/previews and DELETE /api/previews, both superuser — so it is also the first that imports hono, which is a peerDependency at the core's own range because a plugin's routes go on the core's own Hono app.

The rest of the shape — the lockstep version, the peer edge back on the core, npm as the only registry this name is published to — is the template packages/plugin-realtime/README.md describes, and packages/voidbase/test/unit/plugin-extraction.test.ts asserts it over every @voidbase-cloud/plugin-* package in the workspace rather than over any one of them.

Licence

MIT, with voidbase.