brotli-wasm
Advanced tools
A reliable compressor and decompressor for Brotli, supporting node & browsers via wasm
Part of HTTP Toolkit: powerful tools for building, testing & debugging HTTP(S)
A reliable compressor and decompressor for Brotli, supporting node & browsers via wasm
Brotli is available in modern Node (12+) but not older Node or browsers. With this package, you can immediately use it everywhere.
This package contains a tiny wrapper around the compress & decompress API of the Rust Brotli crate, compiled to wasm with just enough setup to make it easily usable from JavaScript.
This is battle-tested, in production use in both node & browsers as part of HTTP Toolkit, and includes automated build with node & browser tests to make sure.
npm install brotli-wasm
You should be able to import this directly into Node, as normal, or in a browser using any bundler that supports ES modules & webassembly (e.g. Webpack v4 or v5, Vite, Rollup, and most others).
For each target (node.js, commonjs bundlers & ESM bundlers) this module exports a different WASM file & setup, with a slightly different entrypoint. These entrypoints all expose a consistent default-export API, in addition to some other exports that may vary (e.g. Node exposes the brotli methods synchronously, while browsers always require an await due to WASM limitations).
In all builds (after waiting for the exported promise in browsers) the module exposes two core methods:
compress(Buffer, [options]) - compresses a buffer using Brotli, returning the compressed buffer. An optional options object can be provided. The only currently supported option is quality: a number between 1 and 11.decompress(Buffer) - decompresses a buffer using Brotli, returning the original raw data.For advanced use data-streaming use cases, CompressStream and DecompressStream classes for streaming compression are also available. See the tests for example usage.
If you want to support node & browsers with the same code, you can use the await browser-compatible form with the default export everywhere.
const brotli = require('brotli-wasm');
const compressedData = brotli.compress(Buffer.from('some input'));
const decompressedData = brotli.decompress(compressedData);
console.log(Buffer.from(decompressedData).toString('utf8')); // Prints 'some input'
import brotliPromise from 'brotli-wasm'; // Import the default export
const brotli = await brotliPromise; // Import is async in browsers due to wasm requirements!
const textEncoder = new TextEncoder();
const textDecoder = new TextDecoder();
const input = 'some input';
const uncompressedData = textEncoder.encode(input);
const compressedData = brotli.compress(uncompressedData);
const decompressedData = brotli.decompress(compressedData);
console.log(textDecoder.decode(decompressedData)); // Prints 'some input'
You can also load it from a CDN like so:
const brotli = await import("https://unpkg.com/brotli-wasm@3.0.0/index.web.js?module").then(m => m.default);
The package itself has no runtime dependencies, although if you prefer using Buffer over using TextEncoder/TextDecoder you may want a browser Buffer polyfill.
If you've installed brotli-wasm as an NPM package, you can load it from your node_modules subfolder:
<!-- index.html -->
<!DOCTYPE html>
<html lang="en">
<head></head>
<body>
<script type="importmap">
{
"imports": {
"brotli-wasm": "/node_modules/brotli-wasm/index.web.js"
}
}
</script>
<script type="module" src="/main.js"></script>
</body>
</html>
// main.js
import brotliPromise from 'brotli-wasm';
const brotli = await brotliPromise;
const input = 'some input';
const uncompressedData = new TextEncoder().encode(input);
const compressedData = brotli.compress(uncompressedData);
const decompressedData = brotli.decompress(compressedData);
console.log(new TextDecoder().decode(decompressedData)); // Prints 'some input'
import brotliPromise from 'brotli-wasm'; // Import the default export
const brotli = await brotliPromise; // Import is async in browsers due to wasm requirements!
const input = 'some input';
// Get a stream for your input:
const inputStream = new ReadableStream({
start(controller) {
controller.enqueue(input);
controller.close();
}
});
// Convert the streaming data to Uint8Arrays, if necessary:
const textEncoderStream = new TextEncoderStream();
// You can use whatever stream chunking size you like here, depending on your use case:
const OUTPUT_SIZE = 100;
// Create a stream to incrementally compress the data as it streams:
const compressStream = new brotli.CompressStream();
const compressionStream = new TransformStream({
transform(chunk, controller) {
let resultCode;
let inputOffset = 0;
// Compress this chunk, producing up to OUTPUT_SIZE output bytes at a time, until the
// entire input has been compressed.
do {
const input = chunk.slice(inputOffset);
const result = compressStream.compress(input, OUTPUT_SIZE);
controller.enqueue(result.buf);
resultCode = result.code;
inputOffset += result.input_offset;
} while (resultCode === brotli.BrotliStreamResultCode.NeedsMoreOutput);
if (resultCode !== brotli.BrotliStreamResultCode.NeedsMoreInput) {
controller.error(`Brotli compression failed when transforming with code ${resultCode}`);
}
},
flush(controller) {
// Once the chunks are finished, flush any remaining data (again in repeated fixed-output
// chunks) to finish the stream:
let resultCode;
do {
const result = compressStream.compress(undefined, OUTPUT_SIZE);
controller.enqueue(result.buf);
resultCode = result.code;
} while (resultCode === brotli.BrotliStreamResultCode.NeedsMoreOutput)
if (resultCode !== brotli.BrotliStreamResultCode.ResultSuccess) {
controller.error(`Brotli compression failed when flushing with code ${resultCode}`);
}
controller.terminate();
}
});
const decompressStream = new brotli.DecompressStream();
const decompressionStream = new TransformStream({
transform(chunk, controller) {
let resultCode;
let inputOffset = 0;
// Decompress this chunk, producing up to OUTPUT_SIZE output bytes at a time, until the
// entire input has been decompressed.
do {
const input = chunk.slice(inputOffset);
const result = decompressStream.decompress(input, OUTPUT_SIZE);
controller.enqueue(result.buf);
resultCode = result.code;
inputOffset += result.input_offset;
} while (resultCode === brotli.BrotliStreamResultCode.NeedsMoreOutput);
if (
resultCode !== brotli.BrotliStreamResultCode.NeedsMoreInput &&
resultCode !== brotli.BrotliStreamResultCode.ResultSuccess
) {
controller.error(`Brotli decompression failed with code ${resultCode}`)
}
},
flush(controller) {
controller.terminate();
}
});
const textDecoderStream = new TextDecoderStream();
let output = '';
const outputStream = new WritableStream({
write(chunk) {
output += chunk;
}
});
await inputStream
.pipeThrough(textEncoderStream)
.pipeThrough(compressionStream)
.pipeThrough(decompressionStream)
.pipeThrough(textDecoderStream)
.pipeTo(outputStream);
console.log(output); // Prints 'some input'
Note that TransformStream has become available in all browsers as of mid-2022: https://caniuse.com/mdn-api_transformstream. It's also been available in Node.js (experimentally) since v16.5.0.
This is a simplified demo example - you may well want to tweak the specific stream buffer sizes for compression/decompression to your use case, to reuse buffers, or explore further optimizations if you're interested in these streaming use cases.
There's a few other packages that do similar things, but I found they were all unusable and/or unmaintained:
FAQs
A reliable compressor and decompressor for Brotli, supporting node & browsers via wasm
The npm package brotli-wasm receives a total of 157,351 weekly downloads. As such, brotli-wasm popularity was classified as popular.
We found that brotli-wasm demonstrated a healthy version release cadence and project activity because the last version was released less than 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.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.
Security News
Research
Socket researchers found a malicious Maven package impersonating the legitimate ‘XZ for Java’ library, introducing a backdoor for remote code execution.