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

@fabric-platform/wasm

v0.7.1

Published

WebAssembly bindings for the Fabric platform SDK

Readme

@fabric-platform/wasm

WebAssembly bindings for the Fabric platform SDK.

A single Rust source-of-truth compiled to both a native rlib (via fabric-platform) and a wasm-bindgen npm package (@fabric-platform/wasm). The model follows Turso's libSQL and ElectricSQL's PGlite — ship one crate, get both a native Rust library and a browser/Node/edge-runtime-ready npm package.

Install

npm install @fabric-platform/wasm

Works in browsers, Node.js ≥ 18, Cloudflare Workers, Deno, and Bun.

Usage

import init, { FabricClient } from "@fabric-platform/wasm";

await init();

const client = new FabricClient("https://api.fabric.example", "sk-...");
client.setOrganizationId("org_123");

// REST
const me = await client.me();
const runId = await client.runWorkflow("video/face-swap", {
  source_url: "https://...",
  target_url: "https://...",
});

// SSE streaming (native browser ReadableStream, async-iterable)
for await (const evt of client.streamWorkflowRun(runId)) {
  console.log(evt.event, evt.data);
}

Why not EventSource?

Browser EventSource cannot set Authorization headers and doesn't support POST. Every authenticated stream would break. We instead use reqwest's streaming response body (backed by fetch's ReadableStream under the hood on wasm, hyper on native) and parse the SSE framing in Rust. Same code path on native and wasm, no browser-specific quirks.

What's wrapped

About a quarter of the full fabric-platform surface is exposed through wasm-bindgen today. See MISSING_METHODS.md for the backlog and priority of the rest. Unwrapped methods are still callable from any other Rust crate depending on fabric-platform compiled to wasm.

Build locally

# Build for browsers
wasm-pack build sdks/rust-wasm --target web --release

# Build for Node / edge runtimes
wasm-pack build sdks/rust-wasm --target nodejs --release

# Build for bundlers (webpack, rollup, vite)
wasm-pack build sdks/rust-wasm --target bundler --release

The resulting pkg/ directory is the npm package. Our CI rewrites its package.json name to @fabric-platform/wasm before publishing.

License

MIT