Security News
Fluent Assertions Faces Backlash After Abandoning Open Source Licensing
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.
LZ4 WASM, ASM.js and CLI for browser and Node with almost native performance. This package includes WASM, ASM.js module and variant that can be used in CLI.
html
<script src="node_modules/lz4/dist/lz4wasm.js"></script>
OR
<script src="node_modules/lz4/dist/lz4asm.js"></script>
npm install lz4-asm
npm install lz4-asm -g
lz4-asm -h
By default module will be exposed as UMD module. In browsers will be defined as window.lz4init
Since WASM modules can't be easily loaded synchronously in browsers some setup for initialization have to be proceed:
lz4init()
call will trigger asyncronous loading of .wasm
file and return instance of lz4modulelz4module
accessible right after lz4init call, but the only safe method to ensure that .wasm
file loading finished - wait for lz4module.ready Promiselz4module.ready
Promise will return fully loaded lz4module instance that can be named lz4
wasm
module, there is predefined lz4.lz4js
property that contains all useful methods and helpers.In short all this flow can be described with next code example:
const lz4module = lz4init();
lz4module.ready.then((lz4) => {
const lz4js = lz4.lz4js;
})
Or even shorter with async/await and Object destructuring
const { lz4js } = await lz4init().ready;
First of all to compile sources in synchronous module mode - set -s WASM_ASYNC_COMPILATION=0
option in gulp/emscripten.js
file for DEV_ARGS
variable.
Then in node env it can be accessed easily const lz4 = lz4init();
that's it.
BUT! There is a big issue in browsers because WASM modules are restricted for synchronous load in main thread.
There are two ways to load it, both require to pass argument into init function lz4init({ wasmBinary: wasmModuleAsArrayBuffer });
where wasmModuleAsArrayBuffer - preloaded file as ArrayBuffer in Uint8Array view representation:
fetch('PATH_TO_WASM_FILE')
.then(response => response.arrayBuffer())
.then(wasmModuleAsArrayBuffer => lz4init({ wasmBinary: wasmModuleAsArrayBuffer }))
.catch(err => {
throw new Error('Failed to load WASM module');
})
.wasm
module as base64, include in bundle, on runtime decode base64 to arrayBuffer and initfunction _base64ToArrayBuffer(base64) {
const binary_string = window.atob(base64);
const binary_length = binary_string.length;
const bytes = new Uint8Array(binary_length);
for (var i = 0; i < binary_length; i++) {
bytes[i] = binary_string.charCodeAt(i);
}
return bytes.buffer;
}
const wasmModuleAsArrayBuffer = _base64ToArrayBuffer(wasmAsBase64);
const lz4 = lz4init({ wasmBinary: wasmModuleAsArrayBuffer });
Both async
(default) and sync
modes available for ASM.js module but with one important difference.
For sync
variant there NO NEED for any extra setup. Set -s WASM_ASYNC_COMPILATION=0
option in gulp/emscripten.js
and simply use as:
const lz4 = lz4init();
It is much easier operate with ASM.js variant is sync mode, but for some cases it operate slower than WASM variant. You can see difference in tests if target different variants in top require
statement.
lz4.BLOCK_MAX_SIZE['64KB']
lz4.BLOCK_MAX_SIZE['256KB']
lz4.BLOCK_MAX_SIZE['1MB']
lz4.BLOCK_MAX_SIZE['4MB']
compress to a lz4 buffer.
Uint8Array | Buffer
Number [4-7]
or as alias lz4.BLOCK_MAX_SIZE["4MB"]
. Available sizes: { "64KB": 4, "256KB": 5, "1MB": 6, "4MB" 7 }
Number [0-1]. Default: 0
, 0: blocks linked, 1: blocks independentNumber [0-1]. Default: 0
, 0: Checksum not available. 1: frame terminated with 32-bit checksum of decompressed dataNumber [0-1]. Default: 0
, Dictionary ID, sent by compressor to help decoder select correct dictionary; 0: no dictID providedNumber [0-1]. Default: 0
, 1: each block followed by a checksum of block's compressed data; 0: disabledNumber [0-16]. Default: 0
, 0: faster but low compression, 16: slower but best compressionNumber [0-1]. Default: 1
, 1: always flush, reduces usage of internal buffers. 0 - flush disabledNumber [0-1]. Default: 1
, 1: parser favors decompression speed vs compression ratio. Only works for high compression modesUint8Array | Buffer
More about options you can find at LZ4 frame description: https://github.com/lz4/lz4/blob/master/doc/lz4_Frame_format.md
decompress a lz4 buffer.
Uint8Array | Buffer
Uint8Array | Buffer
create a nodejs transform stream.
Number [4-7]
or as alias lz4.BLOCK_MAX_SIZE["4MB"]
. Available sizes: { "64KB": 4, "256KB": 5, "1MB": 6, "4MB" 7 }
Number [0-1]. Default: 0
, 0: blocks linked, 1: blocks independentNumber [0-1]. Default: 0
, 0: Checksum not available. 1: frame terminated with 32-bit checksum of decompressed dataNumber [0-1]. Default: 0
, Dictionary ID, sent by compressor to help decoder select correct dictionary; 0: no dictID providedNumber [0-1]. Default: 0
, 1: each block followed by a checksum of block's compressed data; 0: disabledNumber [0-16]. Default: 0
, 0: faster but low compression, 16: slower but best compressionNumber [0-1]. Default: 1
, 1: always flush, reduces usage of internal buffers. 0 - flush disabledNumber [0-1]. Default: 1
, 1: parser favors decompression speed vs compression ratio. Only works for high compression modesMore about options you can find at LZ4 frame description: https://github.com/lz4/lz4/blob/master/doc/lz4_Frame_format.md
create a nodejs transform stream.
Clone the repo.
git clone https://github.com/ukyo/lz4.js.git
Install the dev dependencies.
cd path/to/lz4.js
npm install
Download the original LZ4 repo and compile for development.
npx gulp init
Watch for code updates and run tests.
npx gulp watchDev
Run development tests
Release build.
npx gulp release
buildLib
cleanTest
cleanRelease
compileDev
compileAsmRelease
compileWasmRelease
concatDev
concatAsmRelease
concatWasmRelease
debugTests
fetchLib
rollup
runTests
watchDev
initTask
release
releaseAsm
releaseWasm
testDev
FAQs
A JavaScript binding of LZ4 for the browser.
The npm package lz4-asm receives a total of 5,730 weekly downloads. As such, lz4-asm popularity was classified as popular.
We found that lz4-asm 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
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.
Research
Security News
Socket researchers uncover the risks of a malicious Python package targeting Discord developers.
Security News
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.