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

buttplug-wasm-blob

v3.0.0

Published

Buttplug WASM server binary with typed FFI wrapper

Readme

buttplug-wasm-blob

Patreon donate button Github donate button Discourse Forums Discord bluesky

Buttplug WASM server binary with a typed FFI wrapper. This package bundles a complete Buttplug server compiled to WebAssembly with Web Bluetooth support.

Who is this for?

  • Building your own buttplug client? Use this package directly and write your own connector.
  • Using the official buttplug JS client? Install buttplug-wasm instead, which provides a ready-made connector.

Installation

npm install buttplug-wasm-blob

API

import {
  loadButtplugWasm,
  createServer,
  freeServer,
  sendMessage,
  activateLogging,
} from 'buttplug-wasm-blob';

// Load the WASM module (call once, lazy-loaded)
await loadButtplugWasm();

// Optional: enable debug logging
activateLogging("debug");

// Create a server — the callback receives server events as JSON bytes
const handle = createServer((msg: Uint8Array) => {
  const json = new TextDecoder().decode(msg);
  console.log("Server event:", JSON.parse(json));
});

// Send a message to the server — wrap as JSON array bytes
const request = JSON.stringify({ RequestServerInfo: { Id: 1, ClientName: "MyApp", ProtocolVersionMajor: 4, ProtocolVersionMinor: 0 } });
sendMessage(handle, new TextEncoder().encode('[' + request + ']'), (response: Uint8Array) => {
  console.log("Response:", JSON.parse(new TextDecoder().decode(response)));
});

// Clean up
freeServer(handle);

Message Format

All messages are JSON-encoded Buttplug protocol v4 messages, wrapped in arrays and passed as Uint8Array (UTF-8 bytes). See the Buttplug protocol spec for message formats.

Requirements

  • A browser with Web Bluetooth support (Chrome, Edge, Opera)
  • HTTPS context (Web Bluetooth requires secure origins)

Filing Issues and Contributing

If you have issues or feature requests, please feel free to file an issue.

We are not looking for unsolicited code contributions or pull requests, and will not accept pull requests that do not have a matching issue where the matter was previously discussed in an issue on this repo or in one of our communication channels, listed below.

Pull requests should only be submitted after talking to qdot via issues (or on Discord, our forums, or via DMs on one of our social media accounts if you would like to stay anonymous and out of recorded info on the repo) and receiving approval to develop code based on an issue. Any random or non-issue pull requests will most likely be closed without merging.

If you'd like to contribute in a non-technical way, we need money to keep up with supporting the latest and greatest hardware. We have multiple ways to donate!

License

BSD-3-Clause