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

plasmate-wasm

v0.1.0

Published

Compile HTML to Plasmate SOM in any JavaScript runtime via WebAssembly

Readme

plasmate-wasm

Compile HTML to Plasmate SOM in any JavaScript runtime via WebAssembly. No native binary, no browser engine, no network requests. Just HTML in, structured JSON out.

Install

npm install plasmate-wasm

Usage

Node.js

const { compile, compile_pretty, version } = require('plasmate-wasm');

const html = '<html><body><nav><a href="/about">About</a></nav><main><h1>Hello</h1><p>World</p></main></body></html>';

const somJson = compile(html, 'https://example.com');
const som = JSON.parse(somJson);

console.log(som.title);           // "Hello"
console.log(som.regions.length);   // 2 (navigation + main)
console.log(som.meta.element_count);  // element count

Browser (ES module)

<script type="module">
  import init, { compile } from './plasmate_wasm.js';
  await init();
  
  const som = JSON.parse(compile(htmlString, 'https://example.com'));
</script>

API

compile(html: string, url: string): string

Compile HTML to SOM JSON (compact). The url parameter is used for stable ID generation only; no network request is made.

compile_pretty(html: string, url: string): string

Same as compile but returns pretty-printed JSON.

version(): string

Returns the compiler version.

Why WASM?

The full Plasmate binary includes a browser engine for JavaScript execution and page rendering. That is necessary for fetching live pages but is heavy (large binary, platform-specific).

The SOM compiler itself is pure computation: parse HTML, identify regions, classify elements, generate IDs, serialize JSON. It has no system dependencies and compiles cleanly to WebAssembly.

This package gives you the compiler without the browser. Use it when:

  • You already have the HTML (CMS build pipelines, static site generators)
  • You need to run in environments where native binaries are not available (serverless, edge functions, browsers)
  • You want zero-dependency SOM compilation in any JavaScript runtime

For fetching live pages with JavaScript execution, use the full plasmate CLI or the daemon mode.

Size

The WASM binary is approximately 864KB (before gzip). After gzip compression (typical for CDN delivery), this drops to approximately 300KB.

Links

License

Apache 2.0