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

@marcbachmann/ffprobe

v1.1.3

Published

Node.js native bindings for ffprobe non-blocking file and stream probing

Readme

@marcbachmann/ffprobe

  • No postInstall scripts — installation is a plain file copy, nothing executes
  • No binary downloads — FFmpeg is statically linked into the .node addon; works in air-gapped environments and behind corporate proxies
  • Non-blocking — probing runs inside a Rust thread pool, the Node.js event loop stays free
  • No subprocess overhead — FFmpeg runs in-process, no child_process.spawn per call
  • No system ffprobe required — fully self-contained

Platform support

| Platform | Package | |---|---| | macOS x64 | @marcbachmann/ffprobe-darwin-x64 | | macOS arm64 (Apple Silicon) | @marcbachmann/ffprobe-darwin-arm64 | | Linux x64 (glibc) | @marcbachmann/ffprobe-linux-x64-gnu | | Linux arm64 (glibc) | @marcbachmann/ffprobe-linux-arm64-gnu | | Linux x64 (musl / Alpine) | @marcbachmann/ffprobe-linux-x64-musl | | Linux arm64 (musl / Alpine) | @marcbachmann/ffprobe-linux-arm64-musl | | Windows x64 | @marcbachmann/ffprobe-win32-x64-msvc |

The platform packages are installed automatically as optionalDependencies.

Install

npm install @marcbachmann/ffprobe

Usage

const ffprobe = require('@marcbachmann/ffprobe')

// File path
const result = await ffprobe('/path/to/video.mp4')

// Buffer / Uint8Array (no temp file — FFmpeg reads directly from memory)
const result = await ffprobe(fs.readFileSync('/path/to/video.mp4'))

// Node.js Readable stream
const result = await ffprobe(fs.createReadStream('/path/to/video.mp4'))

// Web ReadableStream
const result = await ffprobe(response.body)

ffprobe returns a Promise<ProbeResult> and never blocks the event loop.

Result shape

interface ProbeResult {
  streams: StreamInfo[]   // video, audio, subtitle tracks
  format?: FormatInfo     // container info: duration, bit_rate, format_name, …
  chapters?: ChapterInfo[]
}

See index.d.ts for the full type definitions.

Environment variables

| Variable | Description | |---|---| | FFPROBE_TMPDIR | Directory used for spill files during stream probing (see below). Defaults to the OS temp directory. |

Stream spilling

When probing a Readable or Web ReadableStream, incoming bytes are buffered in memory up to 512 KiB. If the stream exceeds that threshold, data spills to a temporary file so that FFmpeg can seek backwards — required for formats like MP4 that store their metadata (moov atom) at the end of the file. The temp file is deleted as soon as probing completes.

Set FFPROBE_TMPDIR to control where spill files are written, for example to keep them on a fast local disk or an in-memory filesystem (/dev/shm on Linux).

License

MIT