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

@modplayjs/out-pcm

v0.0.4

Published

PCM file/stream output for the modplayjs tracker player.

Readme

@modplayjs/out-pcm

Offline PCM render + WAV encoder for @modplayjs/core — render a module to float32 stereo (or raw PCM) without a real-time output, and encode it as a WAV file. This is what the verification harness and the studio's export path use.

Install

npm install @modplayjs/out-pcm

Usage

import { CorePlayer } from '@modplayjs/core';
import { plugin as modPlugin } from '@modplayjs/fmt-mod';
import { createSoftMixerPlugin } from '@modplayjs/dsp-softmixer';
import { PcmOutput, createPcmOutput, encodeWavStereo } from '@modplayjs/out-pcm';

const core = new CorePlayer();
core.registries.registerFormat(modPlugin);
core.registries.registerDsp(createSoftMixerPlugin());
core.loadModule(bytes);
core.setDsp('softmixer');
core.startPlayer();

const output = new PcmOutput();
output.start(core);          // renders the whole module now (one-shot, offline)
const pcm = output.getPcm(); // Float32Array — interleaved stereo at core.sampleRate
const wav = output.getWav(); // Uint8Array — 16-bit stereo WAV, ready to save

API

  • PcmOutput — an OutputPlugin (name: 'pcm'). start(core) renders the whole module via core.playBuffer with end-of-song detection (~100 ms chunks, ~10 min safety cap). getPcm() returns the interleaved stereo float32 data; getWav() encodes it as a 16-bit stereo WAV.
  • createPcmOutput() — factory (registerable via core.registries.registerOutput).
  • encodeWavStereo(pcm, sampleRate) → WAV Uint8Array (RIFF header, 16-bit PCM, stereo) — standalone, works on any float32 data.

Part of the modplayjs monorepo. BSD-3-Clause.