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

@altrepo/ffmpeg-kit

v0.2.0

Published

Known-compatible browser ffmpeg.wasm assets with copy and doctor commands.

Readme

@altrepo/ffmpeg-kit

Known-compatible browser ffmpeg.wasm assets with a small CLI for copying and checking them.

Test the package idea in the MP4 to MP3 Converter web version.

Repository: AltRepoYT/altrepo-ffmpeg-kit

This package starts with the legacy browser API because many static apps still expect:

window.FFmpeg.createFFmpeg
window.FFmpeg.fetchFile

The included bundle pins compatible files together:

Install

npm install @altrepo/ffmpeg-kit

Copy Assets

npx altrepo-ffmpeg init public/vendor/ffmpeg

Options:

  • --bundle modern-0.12-mt (Multi-threaded v0.12, fastest but requires COOP/COEP headers)
  • --bundle modern-0.12-st (Single-threaded v0.12, works everywhere)
  • --bundle legacy-0.11 (Default)
  • --force to replace existing files.
  • --types to also copy a TypeScript definition file (ffmpeg-legacy.d.ts) when using the legacy bundle.

Check Assets

npx altrepo-ffmpeg doctor public/vendor/ffmpeg [--bundle modern-0.12-mt]

The doctor command checks that required files exist, are plausible sizes, and that the wrapper/core expose the expected symbols.

Local Development Server

Testing multi-threaded ffmpeg.wasm requires strict Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy headers. You can spin up a local server that automatically injects these headers:

npx altrepo-ffmpeg serve public/ --port 8080

Bundler Configuration

If your bundler (like Vite or Webpack) is trying to bundle the ffmpeg files and breaking them, you can view config snippets to exclude them:

npx altrepo-ffmpeg config vite

Plain HTML

Load the wrapper before your app code:

<script src="/vendor/ffmpeg/ffmpeg.min.js" defer></script>
<script src="/js/app.js" defer></script>

Then initialize with local core files:

const { createFFmpeg, fetchFile } = window.FFmpeg;

const ffmpeg = createFFmpeg({
  log: true,
  corePath: "/vendor/ffmpeg/ffmpeg-core.js"
});

Why This Exists

ffmpeg.wasm is powerful, but browser setup is easy to get wrong. The wrapper, core JS, WASM binary, worker, companion chunks, and API version all have to match. This package makes that boring on purpose.