node-liblzma 2.1.0 → 3.0.0

package/README.md

@@ -3,34 +3,50 @@ Node-liblzma
 
 [![NPM Version](https://img.shields.io/npm/v/node-liblzma.svg)](https://npmjs.org/package/node-liblzma)
 [![NPM Downloads](https://img.shields.io/npm/dm/node-liblzma.svg)](https://npmjs.org/package/node-liblzma)
-[![CI Status](https://github.com/oorabona/node-liblzma/actions/workflows/ci-unified.yml/badge.svg)](https://github.com/oorabona/node-liblzma/actions/workflows/ci-unified.yml)
+[![CI Status](https://github.com/oorabona/node-liblzma/actions/workflows/ci.yml/badge.svg)](https://github.com/oorabona/node-liblzma/actions/workflows/ci.yml)
 [![Documentation](https://img.shields.io/badge/docs-TypeDoc-blue.svg)](https://oorabona.github.io/node-liblzma/)
-
-# What is liblzma/XZ ?
-
-[XZ](https://tukaani.org/xz/xz-file-format.txt) is a container for compressed archives. It is among the best compressors out there according to several benchmarks:
-
-* [Gzip vs Bzip2 vs LZMA vs XZ vs LZ4 vs LZO](http://pokecraft.first-world.info/wiki/Quick_Benchmark:_Gzip_vs_Bzip2_vs_LZMA_vs_XZ_vs_LZ4_vs_LZO)
-* [Large Text Compression Benchmark](http://mattmahoney.net/dc/text.html#2118)
-* [Linux Compression Comparison (GZIP vs BZIP2 vs LZMA vs ZIP vs Compress)](http://bashitout.com/2009/08/30/Linux-Compression-Comparison-GZIP-vs-BZIP2-vs-LZMA-vs-ZIP-vs-Compress.html)
-
-It has a good balance between compression time/ratio and decompression time/memory.
-
-# About this project
-
-This project aims towards providing:
-
-* A quick and easy way to play with XZ compression:
-Quick and easy as it conforms to zlib API, so that switching from __zlib/deflate__ to __xz__ might be as easy as a string search/replace in your code editor :smile:
-
-* Complete integration with XZ sources/binaries:
-You can either use system packages or download a specific version and compile it!
-See [installation](#installation) below.
+[![License](https://img.shields.io/npm/l/node-liblzma.svg)](https://github.com/oorabona/node-liblzma/blob/master/LICENSE)
+[![Node Version](https://img.shields.io/node/v/node-liblzma.svg)](https://nodejs.org)
+[![TypeScript](https://img.shields.io/badge/TypeScript-5.x-blue.svg)](https://www.typescriptlang.org/)
+[![npm provenance](https://img.shields.io/badge/npm-provenance-green.svg)](https://docs.npmjs.com/generating-provenance-statements)
+
+Native Node.js bindings for liblzma — XZ/LZMA2 compression with **browser support via WebAssembly**.
+
+## Table of Contents
+
+- [Quick Start](#quick-start)
+- [What's New](#whats-new)
+  - [v3.0.0 — Browser & WASM Support](#v300--browser--wasm-support)
+  - [v2.0.0 — TypeScript Modernization](#v200--typescript-modernization)
+- [Browser Usage](#browser-usage)
+- [CLI Tool (nxz)](#cli-tool-nxz)
+- [API Reference](#api-reference)
+  - [API Comparison with Zlib](#api-comparison-with-zlib)
+  - [Options](#options)
+- [Advanced Configuration](#advanced-configuration)
+  - [Thread Support](#thread-support)
+  - [Progress Monitoring](#progress-monitoring)
+  - [Concurrency Control (LZMAPool)](#concurrency-control-with-lzmapool)
+  - [File Compression Helpers](#file-compression-helpers)
+  - [Error Handling](#error-handling)
+- [Benchmark](#benchmark)
+- [Installation](#installation)
+- [Testing](#testing)
+- [Migration Guide (v1 → v2)](#migration-guide)
+- [Contributing](#contributing)
+- [Troubleshooting](#troubleshooting)
+- [Bugs](#bugs)
+- [Acknowledgements](#acknowledgements)
+- [License](#license)
+
+## What is liblzma/XZ?
+
+[XZ](https://tukaani.org/xz/xz-file-format.txt) is a container for compressed archives. It offers one of the best compression ratios available, with a good balance between compression time and decompression speed/memory.
 
 > Only LZMA2 is supported for compression output.
-But the library can open and read any LZMA1 or LZMA2 compressed file.
+> But the library can open and read any LZMA1 or LZMA2 compressed file.
 
-# Quick Start
+## Quick Start
 
 ```bash
 npm install node-liblzma
@@ -57,7 +73,8 @@ compressor.on('progress', ({ bytesRead, bytesWritten }) => {
 });
 ```
 
-**Promise style (with `.then()`):**
+<details>
+<summary><strong>Promise style (with .then())</strong></summary>
 
 ```typescript
 import { xzAsync, unxzAsync } from 'node-liblzma';
@@ -75,7 +92,10 @@ xzAsync(Buffer.from('Hello, World!'))
   });
 ```
 
-**Callback style (Node.js traditional):**
+</details>
+
+<details>
+<summary><strong>Callback style (Node.js traditional)</strong></summary>
 
 ```typescript
 import { xz, unxz } from 'node-liblzma';
@@ -89,88 +109,211 @@ xz(Buffer.from('Hello, World!'), (err, compressed) => {
 });
 ```
 
+</details>
+
 📖 **Full API documentation**: [oorabona.github.io/node-liblzma](https://oorabona.github.io/node-liblzma/)
 
-# What's new ?
+## What's New
 
-## Latest Updates (2026)
+### v3.0.0 — Browser & WASM Support
 
-* **Progress Events**: Monitor compression/decompression progress with real-time events
-  ```typescript
-  const compressor = createXz();
-  compressor.on('progress', ({ bytesRead, bytesWritten }) => {
-    console.log(`Read: ${bytesRead}, Written: ${bytesWritten}`);
-  });
-  ```
-* **API Documentation**: Full TypeDoc documentation with Material theme at [oorabona.github.io/node-liblzma](https://oorabona.github.io/node-liblzma/)
-* **XZ Utils 5.8.2**: Updated to latest stable version
+> **[Live Demo](https://oorabona.github.io/node-liblzma/demo/)** — Try XZ compression in your browser.
 
-## Version 2.0 (2025) - Complete Modernization
+- **Browser/WASM support**: Full XZ compression and decompression via WebAssembly
+  - Same API as Node.js (`xzAsync`, `unxzAsync`, `createXz`, `createUnxz`)
+  - WASM binary: ~52KB gzipped (under 100KB budget)
+  - Web Streams API for streaming compression/decompression
+  - Zero-config inline mode: `import from 'node-liblzma/inline'`
+- **CLI tool (nxz)**: Portable xz-like command line tool
+  - Full xz compatibility: `-z`, `-d`, `-l`, `-k`, `-f`, `-c`, `-o`, `-v`, `-q`
+  - Compression presets 0-9 with extreme mode (`-e`)
+  - Progress display, stdin/stdout piping, benchmarking (`-B`)
+- **Progress events**: Monitor compression/decompression in real-time
+- **XZ Utils 5.8.x**: Updated to latest stable version
+- **458+ tests**: Comprehensive test suite with 100% code coverage
 
-This major release brings the library into 2025 with modern tooling and TypeScript support:
+### v2.0.0 — TypeScript Modernization
 
-* **Full TypeScript migration**: Complete rewrite from CoffeeScript to TypeScript for better type safety and developer experience
-* **Promise-based APIs**: New async functions `xzAsync()` and `unxzAsync()` with Promise support
-* **Modern testing**: Migrated from Mocha to Vitest with improved performance and better TypeScript integration
-* **Enhanced tooling**:
-  - [Biome](https://biomejs.dev/) for fast linting and formatting
-  - Pre-commit hooks with nano-staged and simple-git-hooks
-  - pnpm as package manager for better dependency management
-* **Updated Node.js support**: Requires Node.js >= 16 (updated from >= 12)
+- **Full TypeScript migration**: Complete rewrite from CoffeeScript
+- **Promise-based APIs**: `xzAsync()` and `unxzAsync()`
+- **Modern tooling**: Vitest, Biome, pnpm, pre-commit hooks
+- **Node.js >= 16** required (updated from >= 12)
 
-## Legacy (N-API migration)
+<details>
+<summary><strong>Legacy (N-API migration)</strong></summary>
 
-In previous versions, [N-API](https://nodejs.org/api/n-api.html) became the _de facto_ standard to provide stable ABI API for NodeJS Native Modules, replacing [nan](https://github.com/nodejs/nan).
+In previous versions, [N-API](https://nodejs.org/api/n-api.html) replaced [nan](https://github.com/nodejs/nan) as the stable ABI for native modules.
 
-It has been tested and works on:
+Tested on: Linux x64, macOS (x64/arm64), Raspberry Pi 2/3/4, Windows.
 
-* Linux x64 (Ubuntu)
-* OSX (`macos-11`)
-* Raspberry Pi 2/3/4 (both on 32-bit and 64-bit architectures)
-* Windows (`windows-2019` and `windows-2022` are part of GitHub CI)
+**Prebuilt binaries** are bundled for: Windows x64, Linux x64, macOS x64/arm64.
 
-> Notes:
->
-> * For [Windows](https://github.com/oorabona/node-liblzma/actions/workflows/ci-windows.yml)
-> There is no "global" installation of the LZMA library on the Windows machine provisionned by GitHub, so it is pointless to build with this config
->
-* For [Linux](https://github.com/oorabona/node-liblzma/actions/workflows/ci-linux.yml)
+| Flag | Description | Default | Values |
+|------|-------------|---------|--------|
+| `USE_GLOBAL` | Use system liblzma library | `yes` (`no` on Windows) | `yes`, `no` |
+| `RUNTIME_LINK` | Static or shared linking | `shared` | `static`, `shared` |
+| `ENABLE_THREAD_SUPPORT` | Enable thread support | `yes` | `yes`, `no` |
 
-* For [MacOS](https://github.com/oorabona/node-liblzma/actions/workflows/ci-macos.yml)
+If no prebuilt binary matches your platform, `node-gyp` will compile from source automatically.
 
-## Prebuilt images
+</details>
 
-Several prebuilt versions are bundled within the package.
+## Browser Usage
 
-* Windows x86_64
-* Linux x86_64
-* MacOS x86_64 / Arm64
+> **[Live Demo](https://oorabona.github.io/node-liblzma/demo/)** — Try XZ compression in your browser right now.
 
-If your OS/architecture matches, you will use this version which has been compiled using the following default flags:
+node-liblzma v3.0.0+ supports XZ compression in the browser via WebAssembly. The same API works in both Node.js and browsers — bundlers (Vite, Webpack, esbuild) automatically resolve the WASM-backed implementation.
 
-| Flag | Description | Default | Values |
-|------|-------------|---------|--------|
-| `USE_GLOBAL` | Use system liblzma library | `yes` (`no` on Windows) | `yes`, `no` |
-| `RUNTIME_LINK` | Static or shared linking | `shared` | `static`, `shared` |
-| `ENABLE_THREAD_SUPPORT` | Enable thread support | `yes` | `yes`, `no` |
+### Basic Usage
+
+```typescript
+// Bundlers auto-resolve to WASM in browser, native in Node.js
+import { xzAsync, unxzAsync, isXZ } from 'node-liblzma';
+
+// Compress
+const compressed = await xzAsync('Hello, browser!');
+
+// Decompress
+const original = await unxzAsync(compressed);
+
+// Check if data is XZ-compressed
+if (isXZ(someBuffer)) {
+  const data = await unxzAsync(someBuffer);
+}
+```
 
-If not `node-gyp` will automagically start compiling stuff according to the environment variables set, or the default values above.
+### Streaming with Web Streams API
 
-If you want to change compilation flags, please read on [here](#installation).
+```typescript
+import { createXz, createUnxz } from 'node-liblzma';
+
+// Compress a fetch response
+const response = await fetch('/large-file.bin');
+const compressed = response.body.pipeThrough(createXz({ preset: 6 }));
+
+// Decompress
+const decompressed = compressedStream.pipeThrough(createUnxz());
+```
 
-# Related projects
+### Import Modes
 
-Thanks to the community, there are several choices out there:
+| Import | When to use |
+|--------|-------------|
+| `node-liblzma` | Standard — bundler resolves to WASM (browser) or native (Node.js) |
+| `node-liblzma/wasm` | Explicit WASM usage in Node.js (no native addon needed) |
+| `node-liblzma/inline` | Zero-config — WASM embedded as base64 (no external file to serve) |
+
+```typescript
+// Explicit WASM (works in Node.js too, no native build required)
+import { xzAsync } from 'node-liblzma/wasm';
+
+// Inline mode (larger bundle, but no WASM file to configure)
+import { ensureInlineInit, xzAsync } from 'node-liblzma/inline';
+await ensureInlineInit(); // Decodes embedded base64 WASM
+const compressed = await xzAsync(data);
+```
 
-* [lzma-purejs](https://github.com/cscott/lzma-purejs)
-A pure JavaScript implementation of the algorithm
-* [node-xz](https://github.com/robey/node-xz)
-Node binding of XZ library
-* [lzma-native](https://github.com/addaleax/lzma-native)
-A very complete implementation of XZ library bindings
-* Others are also available but they fork "xz" process in the background.
+### Browser Limitations
 
-# API comparison
+- **No sync APIs**: `xzSync()` / `unxzSync()` throw `LZMAError` in browsers
+- **Presets 0-6 only**: Presets 7-9 require more memory than WASM's 256MB limit
+- **No filesystem**: `xzFile()` / `unxzFile()` are not available
+- **No Node Streams**: Use `createXz()` / `createUnxz()` (Web TransformStream) instead of `Xz` / `Unxz` classes
+
+### Bundle Size
+
+| Component | Raw | Gzipped |
+|-----------|-----|---------|
+| liblzma.wasm | ~107KB | ~52KB |
+| Glue code (liblzma.js) | ~6KB | ~2KB |
+| **Total** | **~113KB** | **~54KB** |
+
+For detailed browser setup instructions, see [docs/BROWSER.md](docs/BROWSER.md).
+
+## CLI Tool (nxz)
+
+This package includes `nxz`, a portable xz-like CLI tool that works on any platform with Node.js.
+
+### Installation
+
+```bash
+# Global installation (recommended for CLI usage)
+npm install -g node-liblzma
+
+# Then use directly
+nxz --help
+```
+
+### Quick Examples
+
+```bash
+# Compress a file (creates file.txt.xz, deletes original)
+nxz file.txt
+
+# Decompress (auto-detected from .xz extension)
+nxz file.txt.xz
+
+# Keep original file (-k)
+nxz -k file.txt
+
+# Maximum compression (-9) with extreme mode (-e)
+nxz -9e large-file.bin
+
+# Compress to stdout (-c) for piping
+nxz -c file.txt > file.txt.xz
+
+# List archive info (-l / -lv for verbose)
+nxz -l file.txt.xz
+
+# Benchmark native vs WASM performance (-B)
+nxz -B file.txt
+```
+
+### All Options
+
+| Option | Long | Description |
+|--------|------|-------------|
+| `-z` | `--compress` | Force compression mode |
+| `-d` | `--decompress` | Force decompression mode |
+| `-l` | `--list` | List archive information |
+| `-B` | `--benchmark` | Benchmark native vs WASM performance |
+| `-k` | `--keep` | Keep original file (don't delete) |
+| `-f` | `--force` | Overwrite existing output file |
+| `-c` | `--stdout` | Write to stdout, keep original file |
+| `-o` | `--output=FILE` | Write output to specified file |
+| `-v` | `--verbose` | Show progress for large files |
+| `-q` | `--quiet` | Suppress warning messages |
+| `-0`..`-9` | | Compression level (default: 6) |
+| `-e` | `--extreme` | Extreme compression (slower) |
+| `-h` | `--help` | Show help |
+| `-V` | `--version` | Show version |
+
+<details>
+<summary><strong>One-shot usage (without global install)</strong></summary>
+
+```bash
+# npm/npx
+npx --package node-liblzma nxz --help
+
+# pnpm
+pnpm dlx --package node-liblzma nxz --help
+```
+
+</details>
+
+### Exit Codes
+
+| Code | Meaning |
+|------|---------|
+| 0 | Success |
+| 1 | Error (file not found, format error, etc.) |
+| 130 | Interrupted (SIGINT/Ctrl+C) |
+
+## API Reference
+
+### API Comparison with Zlib
+
+The API mirrors Node.js Zlib for easy adoption:
 
 ```js
 // CommonJS
@@ -193,9 +336,7 @@ import * as lzma from 'node-liblzma';
 | - | `xzFile` | `(input, output, [options])` → `Promise<void>` |
 | - | `unxzFile` | `(input, output, [options])` → `Promise<void>` |
 
-## Options
-
-The `options` object accepts the following attributes:
+### Options
 
 | Attribute | Type | Description | Values |
 |-----------|------|-------------|--------|
@@ -206,15 +347,13 @@ The `options` object accepts the following attributes:
 | `filters` | array | Filter chain | `filter.LZMA2`, `filter.X86`, `filter.ARM`, etc. |
 | `chunkSize` | number | Processing chunk size | Default: 64KB |
 
-For further information about each of these flags, see the [XZ SDK documentation](http://7-zip.org/sdk.html).
+For further information, see the [XZ SDK documentation](http://7-zip.org/sdk.html).
 
 ## Advanced Configuration
 
 ### Thread Support
 
-The library supports multi-threaded compression when built with `ENABLE_THREAD_SUPPORT=yes` (default). Thread support allows parallel compression on multi-core systems, significantly improving performance for large files.
-
-**Thread values:**
+Multi-threaded compression is available when built with `ENABLE_THREAD_SUPPORT=yes` (default).
 
 | Value | Behavior |
 |-------|----------|
@@ -222,26 +361,15 @@ The library supports multi-threaded compression when built with `ENABLE_THREAD_S
 | `1` | Single-threaded (default) |
 | `N` | Use exactly N threads |
 
-**Example:**
-
 ```typescript
 import { createXz, hasThreads } from 'node-liblzma';
 
-// Check if threading is available
 if (hasThreads()) {
-  // Auto-detect: use all CPU cores
-  const compressor = createXz({ threads: 0 });
-
-  // Or specify exact thread count
-  const compressor4 = createXz({ threads: 4 });
+  const compressor = createXz({ threads: 0 }); // auto-detect
 }
 ```
 
-**Important notes:**
-- Thread support only applies to **compression**, not decompression
-- Requires LZMA library built with pthread support (`ENABLE_THREAD_SUPPORT=yes`)
-- Default is `threads: 1` (single-threaded) for predictable behavior
-- Check availability: `hasThreads()` returns `true` if multi-threading is supported
+> **Note**: Threads only apply to compression, not decompression.
 
 ### Progress Monitoring
 
@@ -254,65 +382,52 @@ const compressor = createXz({ preset: 6 });
 
 compressor.on('progress', ({ bytesRead, bytesWritten }) => {
   const ratio = bytesWritten / bytesRead;
-  console.log(`Progress: ${bytesRead} bytes in, ${bytesWritten} bytes out (ratio: ${ratio.toFixed(2)})`);
-});
-
-// Works with both compression and decompression
-const decompressor = createUnxz();
-decompressor.on('progress', ({ bytesRead, bytesWritten }) => {
-  console.log(`Decompressing: ${bytesRead} → ${bytesWritten} bytes`);
+  console.log(`Progress: ${bytesRead} in, ${bytesWritten} out (ratio: ${ratio.toFixed(2)})`);
 });
 
 inputStream.pipe(compressor).pipe(outputStream);
 ```
 
-**Notes:**
-- Progress events fire after each chunk is processed
-- `bytesRead`: Total input bytes processed so far
-- `bytesWritten`: Total output bytes produced so far
-- Works with streams, not buffer APIs (`xz`/`unxz`)
+Progress events fire after each chunk is processed. Works with streams, not buffer APIs.
 
-### Buffer Size Optimization
+### Concurrency Control with LZMAPool
 
-For optimal performance, the library uses configurable chunk sizes:
+For production environments with high concurrency needs:
 
 ```typescript
-const stream = createXz({
-  preset: lzma.preset.DEFAULT,
-  chunkSize: 256 * 1024  // 256KB chunks (default: 64KB)
-});
-```
+import { LZMAPool } from 'node-liblzma';
 
-**Recommendations:**
-- **Small files (< 1MB)**: Use default 64KB chunks
-- **Medium files (1-10MB)**: Use 128-256KB chunks
-- **Large files (> 10MB)**: Use 512KB-1MB chunks
-- **Maximum buffer size**: 512MB per operation (security limit)
+const pool = new LZMAPool(10); // Max 10 concurrent operations
 
-### Memory Usage Limits
+pool.on('metrics', (metrics) => {
+  console.log(`Active: ${metrics.active}, Queued: ${metrics.queued}`);
+});
+
+const compressed = await pool.compress(buffer);
+const decompressed = await pool.decompress(compressed);
+```
 
-The library enforces a 512MB maximum buffer size to prevent DoS attacks via resource exhaustion. For files larger than 512MB, use streaming APIs:
+### File Compression Helpers
 
 ```typescript
-import { createReadStream, createWriteStream } from 'fs';
-import { createXz } from 'node-liblzma';
+import { xzFile, unxzFile } from 'node-liblzma';
 
-createReadStream('large-file.bin')
-  .pipe(createXz())
-  .pipe(createWriteStream('large-file.xz'));
+await xzFile('input.txt', 'output.txt.xz');
+await unxzFile('output.txt.xz', 'restored.txt');
+
+// With options
+await xzFile('large-file.bin', 'compressed.xz', { preset: 9, threads: 4 });
 ```
 
+Handles files > 512MB automatically via streams with lower memory footprint.
+
 ### Error Handling
 
-The library provides typed error classes for better error handling:
+Typed error classes for precise error handling:
 
 ```typescript
 import {
-  xzAsync,
-  LZMAError,
-  LZMAMemoryError,
-  LZMADataError,
-  LZMAFormatError
+  xzAsync, LZMAError, LZMAMemoryError, LZMADataError, LZMAFormatError
 } from 'node-liblzma';
 
 try {
@@ -324,339 +439,106 @@ try {
     console.error('Corrupt data:', error.message);
   } else if (error instanceof LZMAFormatError) {
     console.error('Invalid format:', error.message);
-  } else {
-    console.error('Unknown error:', error);
   }
 }
 ```
 
-**Available error classes:**
-- `LZMAError` - Base error class
-- `LZMAMemoryError` - Memory allocation failed
-- `LZMAMemoryLimitError` - Memory limit exceeded
-- `LZMAFormatError` - Unrecognized file format
-- `LZMAOptionsError` - Invalid compression options
-- `LZMADataError` - Corrupt compressed data
-- `LZMABufferError` - Buffer size issues
-- `LZMAProgrammingError` - Internal errors
-
-### Error Recovery
+**Available error classes**: `LZMAError` (base), `LZMAMemoryError`, `LZMAMemoryLimitError`, `LZMAFormatError`, `LZMAOptionsError`, `LZMADataError`, `LZMABufferError`, `LZMAProgrammingError`.
 
-Streams automatically handle recoverable errors and provide state transition hooks:
+### Buffer Size Optimization
 
 ```typescript
-const decompressor = createUnxz();
-
-decompressor.on('error', (error) => {
-  console.error('Decompression error:', error.errno, error.message);
-  // Stream will emit 'close' event after error
-});
-
-decompressor.on('close', () => {
-  console.log('Stream closed, safe to cleanup');
+const stream = createXz({
+  preset: lzma.preset.DEFAULT,
+  chunkSize: 256 * 1024  // 256KB chunks (default: 64KB)
 });
 ```
 
-### Concurrency Control with LZMAPool
-
-For production environments with high concurrency needs, use `LZMAPool` to limit simultaneous operations:
-
-```typescript
-import { LZMAPool } from 'node-liblzma';
-
-const pool = new LZMAPool(10); // Max 10 concurrent operations
-
-// Monitor pool metrics
-pool.on('metrics', (metrics) => {
-  console.log(`Active: ${metrics.active}, Queued: ${metrics.queued}`);
-  console.log(`Completed: ${metrics.completed}, Failed: ${metrics.failed}`);
-});
+| File Size | Recommended chunkSize |
+|-----------|-----------------------|
+| < 1MB | 64KB (default) |
+| 1-10MB | 128-256KB |
+| > 10MB | 512KB-1MB |
 
-// Compress with automatic queuing
-const compressed = await pool.compress(buffer);
-const decompressed = await pool.decompress(compressed);
+Maximum buffer size: 512MB per operation (security limit). For larger files, use streaming APIs.
 
-// Get current metrics
-const status = pool.getMetrics();
-```
+### Async Callback Contract (errno-based)
 
-**Pool Events:**
-- `queue` - Task added to queue
-- `start` - Task started processing
-- `complete` - Task completed successfully
-- `error-task` - Task failed
-- `metrics` - Metrics updated (after each state change)
+The low-level native callback follows an errno-style contract matching liblzma behavior:
 
-**Benefits:**
-- ✅ Automatic backpressure
-- ✅ Prevents resource exhaustion
-- ✅ Production-ready monitoring
-- ✅ Zero breaking changes (opt-in)
+- **Signature**: `(errno: number, availInAfter: number, availOutAfter: number)`
+- **Success**: `errno` is `LZMA_OK` or `LZMA_STREAM_END`
+- **Error**: any other `errno` value
 
-### File Compression Helpers
-
-Simplified API for file-based compression:
+High-level APIs remain ergonomic — Promise functions resolve to `Buffer` or reject with `Error`, stream users listen to `error` events.
 
-```typescript
-import { xzFile, unxzFile } from 'node-liblzma';
+## Benchmark
 
-// Compress a file
-await xzFile('input.txt', 'output.txt.xz');
+### Performance Hierarchy
 
-// Decompress a file
-await unxzFile('output.txt.xz', 'restored.txt');
+All three backends use the same liblzma library and produce **identical compression ratios**:
 
-// With options
-await xzFile('large-file.bin', 'compressed.xz', {
-  preset: 9,
-  threads: 4
-});
 ```
-
-**Advantages over buffer APIs:**
-- ✅ Handles files > 512MB automatically
-- ✅ Built-in backpressure via streams
-- ✅ Lower memory footprint
-- ✅ Simpler API for common use cases
-
-## Async callback contract (errno-based)
-
-The low-level native callback used internally by streams follows an errno-style contract to match liblzma behavior and to avoid mixing exception channels:
-
-- Signature: `(errno: number, availInAfter: number, availOutAfter: number)`
-- Success: `errno` is either `LZMA_OK` or `LZMA_STREAM_END`.
-- Recoverable/other conditions: any other `errno` value (for example, `LZMA_BUF_ERROR`, `LZMA_DATA_ERROR`, `LZMA_PROG_ERROR`) indicates an error state.
-- Streams emit `onerror` with the numeric `errno` when `errno !== LZMA_OK && errno !== LZMA_STREAM_END`.
-
-Why errno instead of JS exceptions?
-
-- The binding mirrors liblzma’s status codes and keeps a single error channel that’s easy to reason about in tight processing loops.
-- This avoids throwing across async worker boundaries and keeps cleanup deterministic.
-
-High-level APIs remain ergonomic:
-
-- Promise-based functions `xzAsync()`/`unxzAsync()` still resolve to `Buffer` or reject with `Error` as expected.
-- Stream users can listen to `error` events, where we map `errno` to a human-friendly message (`messages[errno]`).
-
-If you prefer Node’s error-first callbacks, you can wrap the APIs and translate `errno` to `Error` objects at your boundaries without changing the native layer.
-
-# Installation
-
-Well, as simple as this one-liner:
-
-```sh
-npm i node-liblzma --save
+System xz  >  nxz native (C++ addon)  >  nxz WASM (Emscripten)
+ fastest        ~1-2x slower               ~2-5x slower (decompress)
+                                           ~1x (compress, large files)
 ```
 
---OR--
+### Full Comparison (246 KB source code, preset 6)
 
-```sh
-yarn add node-liblzma
-```
+| Backend | Compress | Decompress | Size | Environment |
+|---------|----------|------------|------|-------------|
+| **System `xz` 5.8** | 81 ms | 4 ms | 76.7 KB | C binary |
+| **nxz native** | 90 ms | 3.4 ms | 76.7 KB | Node.js + C++ addon |
+| **nxz WASM** | 86 ms | 7.9 ms | 76.7 KB | Node.js + Emscripten |
 
---OR-- (recommended for development)
+### Native vs WASM (nxz -B, preset 6)
 
-```sh
-pnpm add node-liblzma
-```
-
-If you want to recompile the source, for example to disable threading support in the module, then you have to opt out with:
-
-``` bash
-ENABLE_THREAD_SUPPORT=no npm install node-liblzma --build-from-source
-```
-
-> Note:
-Enabling thread support in the library will __NOT__ work if the LZMA library itself has been built without such support.
-
-To build the module, you have the following options:
-
-1. Using system development libraries
-2. Ask the build system to download `xz` and build it
-3. Compile `xz` yourself, outside `node-liblzma`, and have it use it after
-
-## Using system dev libraries to compile
-
-You need to have the development package installed on your system. If you have Debian based distro:
-
-```
-# apt-get install liblzma-dev
-```
-
-## Automatic download and compilation to statically link `xz`
-
-If you do not plan on having a local install, you can ask for automatic download and build of whatever version of `xz` you want.
-
-Just do:
-
-```sh
-npm install node-liblzma --build-from-source
-```
-
-When no option is given in the commandline arguments, it will build with default values.
-
-## Local install of `xz` sources (outside `node-liblzma`)
+| Data | Compress | Decompress | Notes |
+|------|----------|------------|-------|
+| 1 KB text | WASM 2.8x slower | WASM 4.9x slower | Startup overhead dominates |
+| 135 KB binary | ~1:1 | WASM 2x slower | Compression near-parity |
+| 246 KB source | ~1:1 | WASM 2.3x slower | Realistic workload |
+| 1 MB random | ~1:1 | WASM 1.6x slower | Gap narrows with size |
 
-So you did install `xz` somewhere outside the module and want the module to use it.
+<details>
+<summary><strong>Running benchmarks</strong></summary>
 
-For that, you need to set the include directory and library directory search paths as GCC [environment variables](https://gcc.gnu.org/onlinedocs/gcc/Environment-Variables.html).
+```bash
+# Compare nxz (native) vs system xz across file sizes
+./scripts/benchmark.sh
+./scripts/benchmark.sh -s 1,50,200 -p 6,9         # custom sizes/presets
+./scripts/benchmark.sh -o csv > results.csv        # export as CSV/JSON
 
-```sh
-export CPATH=$HOME/path/to/headers
-export LIBRARY_PATH=$HOME/path/to/lib
-export LD_LIBRARY_PATH=$HOME/path/to/lib:$LD_LIBRARY_PATH
+# Compare native addon vs WASM backend
+nxz --benchmark file.txt
+nxz -B -3 large-file.bin                           # with preset 3
 ```
 
-The latest is needed for tests to be run right after.
-
-Once done, this should suffice:
-
-```sh
-npm install
-```
+</details>
 
-# Testing
+### When to Use What
 
-This project maintains **100% code coverage** across all statements, branches, functions, and lines.
+| Scenario | Recommended |
+|----------|-------------|
+| Browser | WASM (only option) |
+| Node.js, performance-critical | Native addon |
+| Node.js, no C++ toolchain available | WASM (`node-liblzma/wasm`) |
+| Cross-platform scripts | nxz CLI |
+| Batch processing many files | System xz |
+| CI/CD with Node.js already installed | nxz CLI |
 
-You can run tests with:
+## Installation
 
-```sh
-npm test
+```bash
+npm install node-liblzma
 # or
-pnpm test
-```
-
-It will build and launch the test suite (325+ tests) with [Vitest](https://vitest.dev/) with TypeScript support and coverage reporting.
-
-Additional testing commands:
-
-```sh
-# Watch mode for development
-pnpm test:watch
-
-# Coverage report
-pnpm test:coverage
-
-# Type checking
-pnpm type-check
-```
-
-# Usage
-
-As the API is very close to NodeJS Zlib, you will probably find a good reference
-[there](http://www.nodejs.org/api/zlib.html).
-
-Otherwise examples can be found as part of the test suite, so feel free to use them!
-They are written in TypeScript with full type definitions.
-
-# Migration Guide
-
-## Migrating from v1.x to v2.0
-
-Version 2.0 introduces several breaking changes along with powerful new features.
-
-### Breaking Changes
-
-1. **Node.js Version Requirement**
-   ```diff
-   - Requires Node.js >= 12
-   + Requires Node.js >= 16
-   ```
-
-2. **ESM Module Format**
-   ```diff
-   - CommonJS: var lzma = require('node-liblzma');
-   + ESM: import * as lzma from 'node-liblzma';
-   + CommonJS still works via dynamic import
-   ```
-
-3. **TypeScript Migration**
-   - Source code migrated from CoffeeScript to TypeScript
-   - Full type definitions included
-   - Better IDE autocomplete and type safety
-
-### New Features You Should Adopt
-
-1. **Promise-based APIs** (Recommended for new code)
-   ```typescript
-   // Old callback style (still works)
-   xz(buffer, (err, compressed) => {
-     if (err) throw err;
-     // use compressed
-   });
-
-   // New Promise style
-   try {
-     const compressed = await xzAsync(buffer);
-     // use compressed
-   } catch (err) {
-     // handle error
-   }
-   ```
-
-2. **Typed Error Classes** (Better error handling)
-   ```typescript
-   import { LZMAMemoryError, LZMADataError } from 'node-liblzma';
-
-   try {
-     await unxzAsync(corruptData);
-   } catch (error) {
-     if (error instanceof LZMADataError) {
-       console.error('Corrupt compressed data');
-     } else if (error instanceof LZMAMemoryError) {
-       console.error('Out of memory');
-     }
-   }
-   ```
-
-3. **Concurrency Control** (For high-throughput applications)
-   ```typescript
-   import { LZMAPool } from 'node-liblzma';
-
-   const pool = new LZMAPool(10); // Max 10 concurrent operations
-
-   // Automatic queuing and backpressure
-   const results = await Promise.all(
-     files.map(file => pool.compress(file))
-   );
-   ```
-
-4. **File Helpers** (Simpler file compression)
-   ```typescript
-   import { xzFile, unxzFile } from 'node-liblzma';
-
-   // Compress a file (handles streaming automatically)
-   await xzFile('input.txt', 'output.txt.xz');
-
-   // Decompress a file
-   await unxzFile('output.txt.xz', 'restored.txt');
-   ```
-
-### Testing Framework Change
-
-If you maintain tests for code using node-liblzma:
-
-```diff
-- Mocha test framework
-+ Vitest test framework (faster, better TypeScript support)
+pnpm add node-liblzma
 ```
 
-### Tooling Updates
-
-Development tooling has been modernized:
-
-- **Linter**: Biome (replaces ESLint + Prettier)
-- **Package Manager**: pnpm recommended (npm/yarn still work)
-- **Pre-commit Hooks**: nano-staged + simple-git-hooks
-
-# Troubleshooting
+### System Libraries
 
-## Common Build Issues
-
-### Issue: "Cannot find liblzma library"
-
-**Solution**: Install system development package or let node-gyp download it:
+If prebuilt binaries don't match your platform, install system development libraries:
 
 ```bash
 # Debian/Ubuntu
@@ -665,374 +547,196 @@ sudo apt-get install liblzma-dev
 # macOS
 brew install xz
 
-# Windows (let node-gyp download and build)
+# Windows (automatic download and build)
 npm install node-liblzma --build-from-source
 ```
 
-### Issue: "node-gyp rebuild failed"
-
-**Symptoms**: Build fails with C++ compilation errors
-
-**Solutions**:
-1. Install build tools:
-   ```bash
-   # Ubuntu/Debian
-   sudo apt-get install build-essential python3
-
-   # macOS (install Xcode Command Line Tools)
-   xcode-select --install
-
-   # Windows
-   npm install --global windows-build-tools
-   ```
-
-2. Clear build cache and retry:
-   ```bash
-   rm -rf build node_modules
-   npm install
-   ```
-
-### Issue: "Prebuilt binary not found"
-
-**Solution**: Your platform might not have prebuilt binaries. Build from source:
+### Build from Source
 
 ```bash
+# Force rebuild with default options
 npm install node-liblzma --build-from-source
-```
-
-## Runtime Issues
-
-### Issue: "Memory allocation failed" (LZMAMemoryError)
-
-**Causes**:
-- Input buffer exceeds 512MB limit (security protection)
-- System out of memory
-- Trying to decompress extremely large archive
-
-**Solutions**:
-1. For files > 512MB, use streaming APIs:
-   ```typescript
-   import { createReadStream, createWriteStream } from 'fs';
-   import { createXz } from 'node-liblzma';
-
-   createReadStream('large-file.bin')
-     .pipe(createXz())
-     .pipe(createWriteStream('large-file.xz'));
-   ```
-
-2. Or use file helpers (automatically handle large files):
-   ```typescript
-   await xzFile('large-file.bin', 'large-file.xz');
-   ```
-
-### Issue: "Corrupt compressed data" (LZMADataError)
-
-**Symptoms**: Decompression fails with `LZMADataError`
-
-**Causes**:
-- File is not actually XZ/LZMA compressed
-- File is corrupted or incomplete
-- Wrong file format (LZMA1 vs LZMA2)
-
-**Solutions**:
-1. Verify file format:
-   ```bash
-   file compressed.xz
-   # Should show: "XZ compressed data"
-   ```
-
-2. Check file integrity:
-   ```bash
-   xz -t compressed.xz
-   ```
-
-3. Handle errors gracefully:
-   ```typescript
-   try {
-     const data = await unxzAsync(buffer);
-   } catch (error) {
-     if (error instanceof LZMADataError) {
-       console.error('Invalid or corrupt XZ file');
-     }
-   }
-   ```
 
-### Issue: Thread support warnings during compilation
-
-**Symptoms**: Compiler warnings about `-Wmissing-field-initializers`
-
-**Status**: This is normal and does not affect functionality. Thread support still works correctly.
-
-**Disable thread support** (if warnings are problematic):
-```bash
+# Disable thread support
 ENABLE_THREAD_SUPPORT=no npm install node-liblzma --build-from-source
 ```
 
-## Performance Issues
-
-### Issue: Compression is slow on multi-core systems
+<details>
+<summary><strong>Custom XZ installation</strong></summary>
 
-**Solution**: Enable multi-threaded compression:
+If you compiled XZ outside of node-liblzma:
 
-```typescript
-import { xz } from 'node-liblzma';
-
-xz(buffer, { threads: 4 }, (err, compressed) => {
-  // 4 threads used for compression
-});
+```bash
+export CPATH=$HOME/path/to/headers
+export LIBRARY_PATH=$HOME/path/to/lib
+export LD_LIBRARY_PATH=$HOME/path/to/lib:$LD_LIBRARY_PATH
+npm install
 ```
 
-**Note**: Threads only apply to compression, not decompression.
-
-### Issue: High memory usage with concurrent operations
-
-**Solution**: Use `LZMAPool` to limit concurrency:
-
-```typescript
-import { LZMAPool } from 'node-liblzma';
+</details>
 
-const pool = new LZMAPool(5); // Limit to 5 concurrent operations
+## Testing
 
-// Pool automatically queues excess operations
-const results = await Promise.all(
-  largeArray.map(item => pool.compress(item))
-);
+```bash
+pnpm test              # Run all 458+ tests
+pnpm test:watch        # Watch mode
+pnpm test:coverage     # Coverage report
+pnpm type-check        # TypeScript type checking
 ```
 
-## Windows-Specific Issues
+Tests use [Vitest](https://vitest.dev/) with 100% code coverage across statements, branches, functions, and lines.
 
-### Issue: Build fails on Windows
+## Migration Guide
 
-**Solutions**:
-1. Install Visual Studio Build Tools:
-   ```powershell
-   npm install --global windows-build-tools
-   ```
+### v1.x → v2.0
 
-2. Use the correct Python version:
-   ```powershell
-   npm config set python python3
-   ```
+<details>
+<summary><strong>Breaking changes and new features</strong></summary>
 
-3. Let the build system download XZ automatically:
-   ```powershell
-   npm install node-liblzma --build-from-source
-   ```
+#### Breaking Changes
 
-### Issue: "Cannot find module" on Windows
+1. **Node.js >= 16** required (was >= 12)
+2. **ESM module format** (`import` instead of `require`)
+3. **TypeScript source** (CoffeeScript removed)
 
-**Cause**: Path separator issues in Windows
+#### New Features
 
-**Solution**: Use forward slashes or `path.join()`:
 ```typescript
-import { join } from 'path';
-await xzFile(join('data', 'input.txt'), join('data', 'output.xz'));
-```
+// Promise-based APIs (recommended)
+const compressed = await xzAsync(buffer);
 
-# Contributing
+// Typed error classes
+import { LZMAMemoryError, LZMADataError } from 'node-liblzma';
 
-We welcome contributions! Here's how to get started.
+// Concurrency control
+const pool = new LZMAPool(10);
+const results = await Promise.all(files.map(f => pool.compress(f)));
 
-## Development Setup
+// File helpers
+await xzFile('input.txt', 'output.txt.xz');
+```
 
-1. **Clone the repository**:
-   ```bash
-   git clone https://github.com/oorabona/node-liblzma.git
-   cd node-liblzma
-   ```
+#### Tooling Changes
 
-2. **Install dependencies** (pnpm recommended):
-   ```bash
-   pnpm install
-   # or
-   npm install
-   ```
+- **Linter**: Biome (replaces ESLint + Prettier)
+- **Tests**: Vitest (replaces Mocha)
+- **Package Manager**: pnpm recommended
 
-3. **Build the project**:
-   ```bash
-   pnpm build
-   ```
+</details>
 
-4. **Run tests**:
-   ```bash
-   pnpm test
-   ```
+## Contributing
 
-## Development Workflow
+We welcome contributions! See the full [contributing guidelines](#development-workflow) below.
 
-### Running Tests
+### Development Setup
 
 ```bash
-# Run all tests
+git clone https://github.com/oorabona/node-liblzma.git
+cd node-liblzma
+pnpm install
+pnpm build
 pnpm test
-
-# Watch mode (re-run on changes)
-pnpm test:watch
-
-# Coverage report
-pnpm test:coverage
-
-# Interactive UI
-pnpm test:ui
 ```
 
-### Code Quality
-
-We use [Biome](https://biomejs.dev/) for linting and formatting:
+### Development Workflow
 
 ```bash
-# Check code style
-pnpm check
-
-# Auto-fix issues
-pnpm check:write
-
-# Lint only
-pnpm lint
-
-# Format only
-pnpm format:write
+pnpm test              # Run tests
+pnpm test:watch        # Watch mode
+pnpm test:coverage     # Coverage report
+pnpm check             # Lint + format check (Biome)
+pnpm check:write       # Auto-fix lint/format
+pnpm type-check        # TypeScript types
 ```
 
-### Type Checking
+We follow [Conventional Commits](https://www.conventionalcommits.org/):
 
-```bash
-pnpm type-check
+```
+feat: add LZMAPool for concurrency control
+fix: resolve memory leak in FunctionReference
+docs: add migration guide for v2.0
 ```
 
-## Code Style
+### Pull Request Process
 
-- **Linter**: Biome (configured in `biome.json`)
-- **Formatting**: Biome handles both linting and formatting
-- **Pre-commit hooks**: Automatically run via nano-staged + simple-git-hooks
-- **TypeScript**: Strict mode enabled
+1. Fork and create a feature branch (`feat/`, `fix/`, `refactor/`, `docs/`)
+2. Add tests for new functionality (100% coverage required)
+3. Run `pnpm check:write && pnpm type-check && pnpm test`
+4. Commit with conventional commits and push
+5. CI checks run automatically on PR
 
-## Commit Convention
+## Troubleshooting
 
-We follow [Conventional Commits](https://www.conventionalcommits.org/):
+<details>
+<summary><strong>Build issues</strong></summary>
 
+**"Cannot find liblzma library"** — Install system dev package:
+```bash
+sudo apt-get install liblzma-dev    # Debian/Ubuntu
+brew install xz                     # macOS
 ```
-<type>(<scope>): <description>
-
-[optional body]
 
-[optional footer]
+**"node-gyp rebuild failed"** — Install build tools:
+```bash
+sudo apt-get install build-essential python3    # Linux
+xcode-select --install                          # macOS
+npm install --global windows-build-tools        # Windows
 ```
 
-**Types**:
-- `feat`: New feature
-- `fix`: Bug fix
-- `docs`: Documentation changes
-- `refactor`: Code refactoring
-- `test`: Test changes
-- `chore`: Build/tooling changes
-- `perf`: Performance improvements
-
-**Examples**:
+**"Prebuilt binary not found"** — Build from source:
 ```bash
-git commit -m "feat(pool): add LZMAPool for concurrency control"
-git commit -m "fix(bindings): resolve memory leak in FunctionReference"
-git commit -m "docs(readme): add migration guide for v2.0"
+npm install node-liblzma --build-from-source
 ```
 
-## Pull Request Process
-
-1. **Fork the repository** and create a feature branch:
-   ```bash
-   git checkout -b feat/my-new-feature
-   ```
-
-2. **Make your changes** following code style guidelines
-
-3. **Add tests** for new functionality:
-   - All new code must have 100% test coverage
-   - Tests go in `test/` directory
-   - Use Vitest testing framework
-
-4. **Ensure all checks pass**:
-   ```bash
-   pnpm check:write   # Fix code style
-   pnpm type-check    # Verify TypeScript types
-   pnpm test          # Run test suite
-   ```
-
-5. **Commit with conventional commits**:
-   ```bash
-   git add .
-   git commit -m "feat: add new feature"
-   ```
-
-6. **Push and create Pull Request**:
-   ```bash
-   git push origin feat/my-new-feature
-   ```
+</details>
 
-7. **Wait for CI checks** to pass (GitHub Actions will run automatically)
+<details>
+<summary><strong>Runtime issues</strong></summary>
 
-## Testing Guidelines
-
-- **Coverage**: Maintain 100% code coverage (statements, branches, functions, lines)
-- **Test files**: Name tests `*.test.ts` in `test/` directory
-- **Structure**: Use `describe` and `it` blocks with clear descriptions
-- **Assertions**: Use Vitest's `expect()` API
-
-**Example test**:
+**LZMAMemoryError** — Input too large for buffer API. Use streaming:
 ```typescript
-import { describe, it, expect } from 'vitest';
-import { xzAsync, unxzAsync } from '../src/lzma.js';
-
-describe('Compression', () => {
-  it('should compress and decompress data', async () => {
-    const original = Buffer.from('test data');
-    const compressed = await xzAsync(original);
-    const decompressed = await unxzAsync(compressed);
-
-    expect(decompressed.equals(original)).toBe(true);
-  });
-});
+createReadStream('large.bin').pipe(createXz()).pipe(createWriteStream('large.xz'));
 ```
 
-## Release Process
+**LZMADataError** — File is not XZ-compressed or is corrupted. Verify with `file compressed.xz` or `xz -t compressed.xz`.
 
-Releases are automated using [@oorabona/release-it-preset](https://github.com/oorabona/release-it-preset):
+**Slow on multi-core** — Enable threads: `createXz({ threads: 0 })` (auto-detect cores).
 
-```bash
-# Standard release (patch/minor/major based on commits)
-pnpm release
+**High memory with concurrency** — Use `LZMAPool` to limit simultaneous operations.
 
-# Manual changelog editing
-pnpm release:manual
+</details>
 
-# Hotfix release
-pnpm release:hotfix
+<details>
+<summary><strong>Windows-specific</strong></summary>
 
-# Update changelog only (no release)
-pnpm changelog:update
+**Build fails** — Install Visual Studio Build Tools and set Python:
+```powershell
+npm install --global windows-build-tools
+npm config set python python3
 ```
 
-**For maintainers only**. Contributors should submit PRs; maintainers handle releases.
+**Path issues** — Use `path.join()` instead of hardcoded separators.
 
-## Getting Help
+</details>
 
-- **Questions**: Open a [Discussion](https://github.com/oorabona/node-liblzma/discussions)
-- **Bugs**: Open an [Issue](https://github.com/oorabona/node-liblzma/issues)
-- **Security**: Email security@example.com (do not open public issues)
+## Related Projects
 
-## License
+- [lzma-purejs](https://github.com/cscott/lzma-purejs) — Pure JavaScript LZMA implementation
+- [node-xz](https://github.com/robey/node-xz) — Node binding of XZ library
+- [lzma-native](https://github.com/addaleax/lzma-native) — Complete XZ library bindings
 
-By contributing, you agree that your contributions will be licensed under [LGPL-3.0+](LICENSE).
+## Bugs
 
-# Bugs
+If you find one, feel free to contribute and post a new [issue](https://github.com/oorabona/node-liblzma/issues)!
+PRs are accepted as well :)
 
-If you find one, feel free to contribute and post a new issue!
-PR are accepted as well :)
+If you compile with threads, you may see warnings about `-Wmissing-field-initializers`.
+This is normal and does not prevent threading from being active and working.
 
-Kudos goes to [addaleax](https://github.com/addaleax) for helping me out with C++ stuff !
+## Acknowledgements
 
-If you compile with threads, you may see a bunch of warnings about `-Wmissing-field-initializers`.
-This is _normal_ and does not prevent threading from being active and working.
-I did not yet figure how to fix this except by masking the warning..
+Kudos to [addaleax](https://github.com/addaleax) for helping out with C++ stuff!
 
-# License
+## License
 
-This software is released under [LGPL3.0+](LICENSE)
+This software is released under [LGPL-3.0+](LICENSE).