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

@immediately-run/worker-transport

v0.1.0

Published

The same-origin worker MessagePort transport (WorkerMessageBus + the {type:'connect'} handshake), extracted so a worker-owning service package can ship its own worker entry without depending on `sandbox`. A leaf package, NOT the SDK (SIMPLIFIED_DEPLOYMENT

Readme

@immediately-run/worker-transport

The same-origin worker MessagePort transport for immediately.run: the WorkerMessageBus request/response protocol and the one-time { type: 'connect' } MessagePort handshake, extracted into a leaf package so a worker-owning service package can ship its own worker entry without depending on sandbox.

Why a dedicated leaf package (not the SDK)

The transport is imported by the worker-owning packages (today @immediately-run/transpiler's Babel worker; later the tsc/eslint/prettier authoring services per R3-107) and by sandbox. Routing it through the SDK would pull the host (immediately-run-site-main) into a build dependency on the app-facing client library — which the host↔SDK design deliberately avoids (the SDK is fetched at runtime, never a host build input; SDK_PACKAGING_SPEC §5). A leaf package keeps the transport entanglement-free. See SIMPLIFIED_DEPLOYMENT_SPEC §14 / roadmap R3-149.

API

  • WorkerMessageBus — the channel-scoped request/response bus over any MessageEndpoint (a Worker, a MessagePort, or self in a worker).
  • bindWorkerMessageBus(self, opts) — installs the { type: 'connect' } handshake on a worker's self: waits for the parent to transfer a MessagePort, starts it, and binds a WorkerMessageBus on it. This is the exact handshake sandbox's babel-worker.ts used, generalized so every worker entry installs it identically.
import { bindWorkerMessageBus } from '@immediately-run/worker-transport';

bindWorkerMessageBus(self, {
  channel: 'sandpack-babel',
  handleRequest: (method, data) =>
    method === 'transform' ? doTransform(data) : Promise.reject(new Error('Unknown method')),
});

Runtime topology

The worker is spawned by the parent page (not the sandboxed iframe) so the iframe can drop allow-same-origin. The parent transfers a MessagePort entangled with one handed into the iframe, so transform requests flow directly between the iframe and the worker (the MessagePort identity rule, HOST_ORIGIN_HARDENING_SPEC §2.4). This package only owns the wire protocol; where the bytes are served from is the consumer's concern.