Packages

@tootallnate/zstd-wasm

0.1.0 · 16 Jun 2026MIT25.1k / weekRepositoryHomepagenpmAtom feed

Your version

Latest releases

  1. 0.1.x · latest line
  2. 0.1.0

    16 Jun 2026
    • Add Zstandard compression support alongside the existing decoder.

      The vendored WASM is now built from upstream zstd 1.5.7's full
      single-file library (encoder + decoder) instead of the decoder-only
      amalgamation, still compiled with wasi-sdk and with no WASI imports.
      New exports mirror the existing decode-side shape:

      The compression level (1–22) is configurable on ZstdEncoder.create,
      ZstdCompressStream, and compressBytes.

  3. 0.0.x · maintenance
  4. 0.0.2

    14 Jun 2026
    • New package: WebAssembly-backed Zstandard decoder for browser and
      Node.js with a streaming TransformStream API.

      @tootallnate/zstd-wasm wraps a build of upstream zstd's
      single-file decoder (compiled with wasi-sdk, no WASI imports) in a
      small TypeScript shim. Exports:

      The caller is responsible for sourcing the WASM bytes (or a
      pre-compiled WebAssembly.Module). The module is published with no
      fetch / fs assumptions so it works equally well in browsers,
      bundlers (vite ?url, webpack asset modules), Node ESM, Deno, etc.
      The compiled WASM is exported at @tootallnate/zstd-wasm/zstd.wasm.

      This package was created to replace fzstd, which has a known
      streaming-decoder correctness bug at large input sizes
      (#19) that produced
      scattered byte corruption in NCZ → NCA pipelines for multi-GB games.

  5. 0.0.0

    14 Jun 2026

Dependency tracking

Know when your own dependencies move

This page watches @tootallnate/zstd-wasm. inlinr reads your package.json and keeps the same watch on every dependency you declare, then tells you only what needs you.

  • Advisories reach you

    An email when a critical or high advisory affects a project, before the next install.

  • Upgrades checked first

    Peer ranges, Node, ESM-only and types changes read before you bump.

  • Only what matters

    Majors and breaking notes stay; patches and sibling bumps fold into one line.

How dependency tracking works

Reading releases, release notes and advisories…

Registry facts last checked 20 Nov 2026. Releases and advisories last read 20 Nov 2026.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.