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

@sproutboat/wire

v0.22.5

Published

Broker frame protocol and the JSON validation utilities it is built on. Single source of truth shared by the CLI dev broker and the platform's edge and supervisor.

Readme

@sproutboat/wire

Broker frame protocol and the JSON validation utilities it is built on. Single source of truth shared by the CLI dev broker and the platform's edge and supervisor.

bun add @sproutboat/wire
import { createBroker } from "@sproutboat/wire";
import { parseJsonValue } from "@sproutboat/wire";

API

  • createBroker(options) opens a binding broker over a resource file: KV, D1, R2, queues, Durable Object storage and alarms, Analytics Engine points, secrets, outbound fetch. Frame envelope, both directions: [u32 LE length][payload].
  • Frame helpers: frameOf, encodeFrame, encodeV1, FRAME_V1, cronMatches, plus the Broker, BrokerOptions, BrokerServer, FetchLike and Frame types.
  • JSON boundary parsing: parseJsonValue, jsonObject, guards (isString, isBoolean, isSafeInteger), JsonValue and JsonObject types. Parse at the I/O boundary, then narrow; nothing downstream takes an unparsed value.

See src/broker.test.ts for the protocol contract in executable form.

Shared SQL execution budgets

Shared mode requires the small SQLite deadline extension. Build it during host or image preparation, before starting the broker, with:

bun packages/wire/src/build-d1-budget.ts

From the published package directory, use bun run build:sql-budget. The build needs a C compiler and SQLite development headers (gcc libsqlite3-dev on Debian/Ubuntu). It uses SQLite's extension ABI and does not link another SQLite engine on Linux. Native outputs are host-specific and excluded from the source package. The platform installer builds the extension during provisioning and staged updates; tenant requests never invoke a compiler.

The default shared D1 execution budget is 1,000 ms per operation, including an entire transactional batch. Operators can set SPROUTBOAT_D1_EXECUTION_MS to an integer from 10 to 30,000. Queue admission remains 128 active/queued calls per broker, 16 per session, with a separate ten-second queue deadline. Tenant request fields cannot change execution budgets.

A native progress callback checks the monotonic deadline every 1,000 SQLite VM instructions. Interrupted batches roll back, and the same SQL lane remains usable. Multi-statement exec retains SQLite's existing partial-commit behavior: earlier statements can have committed before a later statement fails. The executor never automatically retries uncertain mutations.

Locks and other native operations may not poll SQLite progress. A broker-thread watchdog allows one additional second, then revokes the broker and all of its sessions through supervisor recovery. That fallback reports an uncertain SQL outcome; it does not assert that every earlier mutation rolled back. Shared mode remains opt-in, and this mechanism is not a memory isolation boundary.

On macOS, Bun's default Apple SQLite disables extensions. Install an extension-capable SQLite library and select it before opening any SQLite DBs. The shared broker and package test preload select Homebrew's standard library location; SPROUTBOAT_D1_SQLITE_LIBRARY overrides it. SQLITE_INCLUDE overrides the build header directory, and SPROUTBOAT_D1_BUDGET_EXTENSION overrides the trusted extension path. Linux uses Bun's existing SQLite engine. Dedicated broker mode does not enable execution budgets.