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

@sorisdk/web-audio

v0.1.5

Published

Web SDK for browser-based audio recognition with SORI API

Downloads

1,023

Readme

@sorisdk/web-audio

Web SDK for integrating SORI audio recognition into browser-based services.

This package provides the browser-side flow needed for web recognition, including authentication bootstrap, pack caching, microphone input, audio fingerprint generation, matching, and campaign events.

Public integration guide: https://docs.soriapi.com/ko/integration/web

Requirements

  • A secure context such as https:// or http://localhost
  • A modern browser with AudioContext and MediaDevices.getUserMedia()
  • An ephemeral key issued by your server
  • Microphone permission granted by the user

Installation

npm install @sorisdk/web-audio

Vite-based apps need vite-plugin-wasm.

import wasm from "vite-plugin-wasm";

export default {
  plugins: [wasm()]
};

The default wasm initialization path is intended to work in both Vite dev/build and Nuxt client production bundles without extra loader patching.

Minimal example

import { AudioRecognizer } from "@sorisdk/web-audio";

const recognizer = new AudioRecognizer({
  appId: "YOUR_APP_ID",
  ephemeralKey: async () => {
    const response = await fetch("/api/ephemeral-key", {
      method: "POST"
    });

    if (!response.ok) {
      throw new Error(`Ephemeral key request failed: HTTP ${response.status}`);
    }

    const { ephemeral_key } = await response.json();
    return ephemeral_key;
  }
});

recognizer.on("campaign", (event) => {
  console.log(event.campaign);
});

recognizer.on("error", ({ error }) => {
  console.error(error);
});

await recognizer.start();

Call stop() or destroy() when recognition should end or when the page is being cleaned up.

await recognizer.stop();
await recognizer.destroy();

Advanced wasm loading overrides

If you need to pin explicit generated modules, use the nested wasm options:

import { AudioRecognizer } from "@sorisdk/web-audio";

const recognizer = new AudioRecognizer({
  appId: "YOUR_APP_ID",
  ephemeralKey: async () => "YOUR_EPHEMERAL_KEY",
  wasm: {
    afpgen: {
      loader: () => import("@sorisdk/afpgen/generated/core.js")
    },
    matcher: {
      loader: () => import("@sorisdk/matcher/generated/core.js")
    },
    matchWindow: {
      loader: () => import("@sorisdk/web-audio/generated/window.js")
    }
  }
});

Integration flow

  1. Prepare your appId and ephemeral key flow.
  2. Create an AudioRecognizer.
  3. Subscribe to the events you need, such as campaign, match, and error.
  4. Call start() to begin recognition.
  5. Call stop() or destroy() when leaving the page or stopping capture.

Recommendations

  • Do not hardcode ephemeral keys in the browser. Issue them from your server.
  • Show clear UI while the microphone is active.
  • Use the public documentation for full setup details and caveats.