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

wasm-os-sdk

v0.1.0

Published

JS SDK for wasm-os devices: serial protocol, device client, and Node/Web Serial transports

Readme

wasm-os SDK

Isomorphic JavaScript SDK for talking to ESP32 devices running the wasm-os firmware: the binary serial protocol, a transport-agnostic device client, and transports for Node (node-serialport) and the browser (Web Serial API).

The protocol layer is pure Uint8Array/DataView — no Node Buffer — so the same code runs unbundled in the browser. serialport is an optional peer dependency, required lazily only by the Node transport.

Node

const { autoDetectPort, openNodeSerialTransport, createDeviceClient } = require("wasm-os-sdk");

const portPath = await autoDetectPort();
const transport = await openNodeSerialTransport(portPath);
const client = createDeviceClient(transport);

await client.pushFile(wasmBytes, "main.wasm", {
  onProgress: (sent, total) => console.log(`${sent}/${total}`),
});
await transport.close();

Browser (Chromium-only Web Serial)

import { openWebSerialTransport, createDeviceClient } from "wasm-os-sdk";

const serialPort = await navigator.serial.requestPort();
const transport = await openWebSerialTransport(serialPort);
const client = createDeviceClient(transport);

await client.pushFile(wasmBytes, "main.wasm");
await transport.close();

API

  • protocol.js — frame building/parsing, shared byte-for-byte with wasm-os-core/main/serial_cmd.c (keep the two in sync)
  • createDeviceClient(transport)pushFile(data, name, {onProgress, beginAttempts}), deleteFile(name), restart(), plus raw sendFrame/sendFrameWithRetry
  • hardReset(transport) — reboot into the application (device settings are read once at boot)
  • Transports implement { write, subscribe, setSignals, close }; anything matching that shape works with the client.
  • parsePartitionTable(image) / findPartition(image, label) — read the ESP-IDF partition table out of a merged firmware image

littlefs image building lives in the sibling mklfs package.

Tests

npm test   # protocol unit tests, no hardware