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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@jitsi/rnnoise-wasm

v0.2.0

Published

Rnnoise sub-module compiled with emscripten as web assembly module

Downloads

4,161

Readme

rnnoise-wasm

rnnoise noise suppression library as a WASM module.

This repository contains the necessary utilities to build the library using a Docker build environment with Emscripten.

Build

Prerequisites

  • node - tested version v10.16.3
  • npm - tested version v6.9.0
  • docker - tested version 19.03.1

Building the module

Building is straightforward, run:

npm run build

The repository already has a pre-compiled version under the dist folder, running the above command will replace it with the newly compiled binaries and glue wasm .js file respectively.

In order to facilitate the build with docker the following prebuilt image is used trzeci/emscripten/ however, it is slightly altered by installing autotools components necessary for building rnnoise.

In summary the build process consists of two steps:

  1. build:dockerfile - pulls in trzeci/emscripten/ which is then altered and saved. Any suqsequent build is going to check if the images was already installed and use that, so if one wants to make changes to the Dockerfile be sure to first delete the build image from your local docker repo.
  2. build:emscripten - mounts the repo to the docker image from step one and runs build.sh on it. The bash script contains all the steps necessary for building rnnoise as a wasm module.

Usage

Currently the prebuilt files rnnoise.wasm along with the index.js are genererated using the old rnnoise release 0.1 while the sync version is generated using 0.2. This is done to keep compatibility with usage in jitsi meet, namely the old async version is used for noise detection while the new sync model is used for actual noise suppression within the context of an AudioWorklet. This will change in the future when jitsi meet noise detection will have updated heuristics using the new model. However, following a build all files in the dist files will be replaced with versions using the new model (both sync and async). Files replaced include the actual webassembly binary rnnoise.wasm and the generated emscriten.js file named rnnoise.js which contains glue code and the necessary libc runtime javascript bindings, as well as the rnnoise-sync.js file which is the sync loading version that has the binary wasm module inlined as a base64 string, this is useful for contexts that only allow synchronous loading of resources, like an AudioWorklet.

The repo is structured so it can be used as a npm dependency, with the entry point in dist/index.js, be mindful as using index.js automatically implies that rnnoise.wasm needs to be present as well, thus for a normal npm build system one must explicitly copy rnnoise.wasm to the project structure.