Back to Explore

Brooooooklyn/lzma

GitHub
2 updates · last 90 days1 watchersOpen source

Last release:

@napir-rs/lzma provides `lzma`, `lzma2`, and `xz` compression and decompression for Node.js and the browser. It exposes one-shot and streaming APIs, using the pure-Rust `lzma-rust2` crate via `napi-rs`.

Project status

  • Actively maintained: GitHub shows an upstream push on 2026-09-28, and the repo had recent updates in July 2026 (v1.5.0 and v1.5.1), indicating ongoing maintenance rather than dormancy.
  • Update cadence: Two updates were published within about a day (v1.5.0 on 2026-07-13, v1.5.1 on 2026-07-14). After that, there were no published updates between mid-July and early October 2026, though there was at least one upstream push on 2026-09-28.

AI summary generated

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • v1.5.1

    Release v1.5.1 is primarily a CI change intended to prevent a stale x64 host helper binary from being uploaded during cross-build publishing. In addition to the CI adjustment, the runtime entrypoint code was updated to enforce native binding package version matching against 1.5.1.

  • v1.5.0

    v1.5.0 adds streaming compression and decompression APIs for lzma, lzma2, and xz, including incremental class-based APIs and Web Streams support. The release notes also include a large set of dependency and CI updates, plus a N-API bump for an off-thread drop fix and some documentation changes.

    Features
  • v1.4.5

    v1.4.5 primarily updates internal dependencies and CI tooling. However, the actual code diff also changes the public API surface by removing the exported Lzma class from the TypeScript typings and WASI wrappers, and it adds a native binding version check that can throw at runtime under certain environment variable settings.

    Breaking
  • v1.4.4

    v1.4.4 primarily upgrades the project to NAPI-RS 3.0 stable, along with various build and tooling dependency updates. The code diff also shows API surface expansion (a new Lzma class export) and a behavioral change in the WASI worker lifecycle.

    Features
  • v1.4.3

    v1.4.3 includes a documented fix to the `browser` field in `package.json` plus dependency/lockfile maintenance. However, the code diff also shows multiple packaging and export-shape changes (CommonJS and WASI browser/CJS builds) and build toolchain adjustments that are not mentioned in the release notes.

  • v1.4.2

    v1.4.2 is primarily a dependency and CI maintenance release, with many chore updates (esbuild, yarn, oxlint, @types/node, etc.) and a CI pipeline update. The code diff also shows several runtime and build-behavior changes in the JS loaders and Rust runtime that are not mentioned in the release notes.

  • v1.4.1

    v1.4.1 is a small release focused on fixing how the package is exported for browser/bundler usage. The diff shows changes only to packaging metadata (package.json) and the changelog, with a version bump to 1.4.1.

  • v1.4.0

    v1.4.0 is primarily a dependency and CI maintenance release, including updates to Yarn, esbuild, oxlint, and Rust crate versions (napi and napi-derive) plus broader CI coverage across more targets. Despite the release notes focusing on CI and dependency bumps, the code diff shows changes to the public TypeScript API surface and the underlying N-API binding input types.

  • v1.3.1

    Release v1.3.1 mainly updates the npm package metadata to improve browser bundling. The code diff shows a version bump plus packaging changes that add a browser entrypoint, without any API or type changes visible in the provided diff.

  • v1.3.0

    No publisher release notes were provided for v1.3.0. Based on the code diff, this release primarily introduces WASI WebAssembly support (including browser and node entrypoints) and refactors how the native bindings are selected and loaded at runtime, along with several build and CI changes.