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

@smallstack/web-component-bridge-protocol

v1.0.0

Published

Single source of truth for the postMessage bridge protocol between the smallstack Business Platform host page and sandboxed third-party web components

Downloads

341

Readme

@smallstack/web-component-bridge-protocol

The typed postMessage protocol between the smallstack Business Platform host page and a sandboxed third-party web component. This is the single source of truth for the bridge envelope, constants, payload types, and the createBridgeMessage / parseBridgeMessage codec — a tiny, zero-dependency module both sides depend on:

  • Platform@smallstack/shared (in smallstack/business-platform) will re-export this module once it adopts the package (a follow-up to the initial publish); the host page and host-side bridge use it. Until then the platform keeps its own copy.
  • SDK@smallstack/web-component-sdk depends on it; the component-side client and mock host use it.

Release rule (protocol version ⇄ semver major)

The package's semver major equals WEB_COMPONENT_BRIDGE_PROTOCOL_VERSION.

Any breaking change to the wire envelope (message types, payload shapes, validation) is a major bump here, which forces a major bump of every consumer:

  1. Bump WEB_COMPONENT_BRIDGE_PROTOCOL_VERSION and this package's major.
  2. Publish the new major.
  3. Bump @smallstack/web-component-sdk's major to match (SDK 1.x ⇄ protocol 1) and update its dependency range.
  4. Bump the dependency range in @smallstack/shared (smallstack/business-platform).

Because a stale bundle carries the old version, parseBridgeMessage rejects it — a protocol mismatch fails loudly at the boundary instead of subtly.

Usage

import {
	createBridgeMessage,
	parseBridgeMessage,
	WEB_COMPONENT_BRIDGE_PROTOCOL_VERSION
} from "@smallstack/web-component-bridge-protocol";

const message = createBridgeMessage(nonce, "resize", { height: 120 });
const parsed = parseBridgeMessage(event.data, { nonce }); // null if invalid