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

audio-snip

v0.3.0

Published

Decode audio segments from remote files via HTTP Range requests

Downloads

314

Readme

audio-snip

Decode a segment of a remote audio file via HTTP Range requests — without downloading the whole thing.

A 50 MB podcast, but you only need seconds 30–60? audio-snip fetches ~500 KB instead of 50 MB.

Demo

Live demo — pick a test file, choose a time range, see exactly which byte ranges were fetched.

Before / After

Before — vanilla fetch + AudioContext

You have to download the entire file, then decode, then slice:

const resp = await fetch(url);               // downloads all 50 MB
const buf = await resp.arrayBuffer();
const full = await audioCtx.decodeAudioData(buf);

// manual trimming
const start = Math.round(30 * full.sampleRate);
const end = Math.round(60 * full.sampleRate);
const trimmed = audioCtx.createBuffer(full.numberOfChannels, end - start, full.sampleRate);
for (let ch = 0; ch < full.numberOfChannels; ch++) {
  trimmed.copyToChannel(full.getChannelData(ch).subarray(start, end), ch);
}

After — audio-snip

import { audioSnip } from 'audio-snip';
import { Mp3Plugin } from 'audio-snip/mp3';
import { Mp4Plugin } from 'audio-snip/mp4';

audioSnip.register(new Mp3Plugin());
audioSnip.register(new Mp4Plugin());

const buffer = await audioSnip.decodeAudioDataSegment(audioCtx, url, 30, 60);
// AudioBuffer with exactly 30 seconds of audio
// only a few hundred KB were fetched

How it works

  1. Fetch file header (first ~128 KB) to parse codec metadata
  2. Use metadata (Xing TOC for MP3, stbl tables for MP4) to map time → byte offset
  3. Fetch only the needed byte range via HTTP Range request
  4. Decode and trim to exact sample boundaries

Supported formats

| Format | Plugin | Notes | |--------|--------|-------| | MP3 CBR/VBR | Mp3Plugin | Xing/VBRI TOC, LAME gapless, ID3v2 | | M4A/MP4/AAC | Mp4Plugin | Uses mp4box.js, ADTS wrapping, video+audio files |

Install

npm install audio-snip

License

MIT