Security News
Node.js EOL Versions CVE Dubbed the "Worst CVE of the Year" by Security Experts
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
exec-buffer
Advanced tools
The exec-buffer npm package is a utility for executing a buffer, typically used for processing images or other binary data. It provides a simple interface to run a binary and buffer the output, making it useful for tasks that involve manipulating binary data streams.
Execute a binary with input and output buffers
This feature allows you to execute a binary with input and output buffers. In this example, the input buffer is read from 'input.png', processed by the 'optipng' binary, and the output buffer is written to 'output.png'.
const execBuffer = require('exec-buffer');
const fs = require('fs');
const path = require('path');
const execa = require('execa');
(async () => {
const input = fs.readFileSync('input.png');
const output = await execBuffer({
input,
bin: 'optipng',
args: ['-out', execBuffer.output]
});
fs.writeFileSync('output.png', output);
})();
Execa is a modern alternative to child_process for executing external binaries. It provides a more user-friendly API and better defaults. Unlike exec-buffer, execa does not specifically focus on buffering binary data but is more general-purpose for executing commands.
The child_process module is a core Node.js module that provides the ability to spawn child processes. It is more low-level compared to exec-buffer and requires more boilerplate code to handle buffers and streams.
The buffer module is a core Node.js module that provides a way to handle binary data directly. While it does not execute binaries, it is often used in conjunction with other modules like child_process to manage binary data streams.
Run a Buffer through a child process
$ npm install exec-buffer
const fs = require('fs');
const execBuffer = require('exec-buffer');
const gifsicle = require('gifsicle').path;
execBuffer({
input: fs.readFileSync('test.gif'),
bin: gifsicle,
args: ['-o', execBuffer.output, execBuffer.input]
}).then(data => {
console.log(data);
//=> <Buffer 47 49 46 38 37 61 ...>
});
Type: Object
Type: Buffer
The Buffer
to be ran through the child process.
Type: string
Path to the binary.
Type: Array
Arguments to run the binary with.
Type: string
Default: tempfile()
Where input
will be written to. In most cases you don't need to set this.
Type: string
Default: tempfile()
Where output file will be written to. In most cases you don't need to set this.
Returns a temporary path to where the input file will be written.
Returns a temporary path to where the output file will be written.
MIT © Kevin Mårtensson
FAQs
Run a buffer through a child process
The npm package exec-buffer receives a total of 418,852 weekly downloads. As such, exec-buffer popularity was classified as popular.
We found that exec-buffer 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
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.