![require(esm) Backported to Node.js 20, Paving the Way for ESM-Only Packages](https://cdn.sanity.io/images/cgdhsj6q/production/be8ab80c8efa5907bc341c6fefe9aa20d239d890-1600x1097.png?w=400&fit=max&auto=format)
Security News
require(esm) Backported to Node.js 20, Paving the Way for ESM-Only Packages
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
ffmpeg-installer-gl
Advanced tools
Platform independent binary installer of FFmpeg for node projects
Platform independent binary installer of FFmpeg for node projects. Useful for tools that should "just work" on multiple environments.
Installs a binary of ffmpeg
for the current platform and provides a path and version. Supports Linux, Windows and Mac OS/X.
A combination of package.json fields optionalDependencies
, cpu
, and os
let's the installer only download the binary for the current platform. See also "Warnings during install", below.
npm install --save @ffmpeg-installer/ffmpeg
const ffmpeg = require('@ffmpeg-installer/ffmpeg');
console.log(ffmpeg.path, ffmpeg.version);
const ffmpegPath = require('@ffmpeg-installer/ffmpeg').path;
const spawn = require('child_process').spawn;
const ffmpeg = spawn(ffmpegPath, args);
ffmpeg.on('exit', onExit);
const ffmpegPath = require('@ffmpeg-installer/ffmpeg').path;
const ffmpeg = require('fluent-ffmpeg');
ffmpeg.setFfmpegPath(ffmpegPath);
To automatically choose the binary to install, optionalDependencies are used. This currently outputs warnings in the console, an issue that is tracked by the npm team here.
If you get permissions issues, try adding a .npmrc file with the following:
unsafe-perm=true
See issue #21
It's a known issue that Asar breaks native paths. As a workaround, if you use Asar, you can do something like this:
const ffmpegPath = require('@ffmpeg-installer/ffmpeg').path.replace('app.asar', 'app.asar.unpacked');
If you need to install a version of ffmpeg
that differs than your current platform (e.g. compiling a Linux version to upload to AWS Lambda from MacOS), you can use npm install @ffmpeg-installer/linux-x64 --force
(substituting linux-x64
with whatever platform you need). Note that if you are compressing your project into a .zip
for Lambda, you will need to exclude the other platforms' builds from your archive.
Downloaded from the sources listed at ffmpeg.org:
For version updates, submit issue or pull request.
In every updated platforms/*
directory:
npm run upload
FAQs
Platform independent binary installer of FFmpeg for node projects
The npm package ffmpeg-installer-gl receives a total of 0 weekly downloads. As such, ffmpeg-installer-gl popularity was classified as not popular.
We found that ffmpeg-installer-gl demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
Security News
PyPI now supports iOS and Android wheels, making it easier for Python developers to distribute mobile packages.
Security News
Create React App is officially deprecated due to React 19 issues and lack of maintenance—developers should switch to Vite or other modern alternatives.