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

@polyphony-chat/polyproto

v0.1.0

Published

WebAssembly bindings for polyproto

Readme

polyproto-wasm

The polyproto-wasm crate wraps the Rust implementation of polyproto. It is, sort of, a facade, exposing the Rust implementation in a manner that is compatible with wasm-bindgen/JavaScript.

Architectural Concerns

The idea behind choosing something resembling the facade pattern to expose the polyproto Rust SDK to JavaScript has been a result of the following constraints:

  1. I (ava) am the sole active maintainer of this crate and most of the polyproto ecosystem. I am limited by resources such as time and (emotional) energy. Because of these constraints, I cannot "afford" to write a JavaScript implementation of polyproto from scratch. Reusing what we already have is a smart idea for this.
  2. A polyproto library for JavaScript is needed for many reasons. Most notably: sonata aims to ship a small prototype with some interactivity, so that individuals have something to try polyproto out with. This could be done in Rust too, through yew, dioxus, leptos or another Rust-based frontend framework, but, ultimately, JavaScript is the standard for interactive web applications, and it would be rather pointless to save a little work now (by staying completely in Rust land), only to still have to provide a JavaScript implementation of the polyproto SDK in the near future, for purposes of building a client, as well as creating an actual developer ecosystem around polyproto.
  3. For reasons outlined in 1., there was the need for some sort of abstraction that is easy to maintain. Even when some implementation details change in the Rust implementation, it should be easy to port them over to WASM. A facade fulfills this by latching onto the public API of polyproto-rs (which, public APIs should change/break only rarely), and, by polyproto-wasm being in the same worktree as polyproto-rs, changes in polyproto-rs can be propagated instantly to polyproto-wasm, and breaking changes always get noticed, as both crates are part of the same CI pipeline.