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

rollup-plugin-wasm-module

v0.0.3

Published

A Rollup plugin that wraps wasm-module-preprocessor.

Downloads

34

Readme

rollup-plugin-wasm-module

A Rollup plugin that wraps wasm-module-preprocessor.

Install

npm install --save-dev rollup-plugin-wasm-module

Usage

rollup-plugin-wasm-module by default loads wasm modules asynchronously, and takes an optional importObject. All wasm modules are validated on build, so that there is no need for runtime testing and beyond just validating wasm modules, the size of the wasm module is checked too.

Async

file.js

import wasmModule from 'factorial.wasm';

export default async () => {
  const {
    instance: {
      exports: {
        factorial = () => undefined,
      },
    },
  } = await wasmModule(
    // Add an optional `importObject`:
    // {
    //   global: {},
    //   env: {},
    // }
  );

  return factorial(number);
}

rollup.config.js

import wasmModule from 'rollup-plugin-wasm-module';

export default {
  plugins: [
    wasmModule({
      options: {
        // Defaults to:
        // sync: false,
      }
    }),
  ],
};

Sync

file.js

import wasmModule from 'factorial.wasm';

export default () => {
  const {
    exports: {
      factorial = () => undefined,
    },
  } = wasmModule(
    // Add an optional `importObject`:
    // {
    //   global: {},
    //   env: {},
    // }
  );

  return factorial(number);
}

rollup.config.js

import wasmModule from 'rollup-plugin-wasm-module';

export default {
  plugins: [
    wasmModule({
      options: {
        // Only use this for small wasm modules. The max size of the binary
        // will, by default, be restricted to less than 4KiB.
        sync: false,
      }
    }),
  ],
};

Options

All options are defined by and are passed directly to wasm-module-preprocessor; check its documentation for more a in-depth explanation.