Back to Explore

xtuc/webassemblyjs

GitHub
1 watchersOpen source

Last release:

webassemblyjs is a JavaScript toolchain for working with WebAssembly, including parsing and interpreting modules, working with the WebAssembly text format (WAST), and printing or optimizing binaries. It also provides utilities like AST helpers, validation, and tools for editing or stripping parts of WASM binaries, plus a WebAssembly REPL and a Webpack loader for WAST.

Project status

  • Maintenance status: Based on the last upstream push (2025-01-27) and the most recent observed updates (mostly in Nov 2024), xtuc/webassemblyjs appears quiet or in maintenance mode, not actively maintained as of 2026-08-12.
  • Update cadence: There is evidence of tight version-bump activity in a short window (many monorepo version-only updates on 2024-11-06), followed by a long gap with no subsequent updates shown into 2025-01-27 and beyond.

AI summary generated

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

Recent updates

  • v1.14.1

    Release v1.14.1 does not include any publisher-provided release notes. The provided diff shows only monorepo metadata and dependency version alignment changes across many packages, not application/source code changes.

  • v1.14.0

    Release v1.14.0 has no documented release notes content (publisher provided none). The code diff shows the change is limited to monorepo metadata, with package versions bumped to 1.14.0 and internal dependency references updated accordingly.

  • v1.13.4

    Release v1.13.4 contains no publisher release notes. The code diff provided shows a monorepo version bump across many packages, primarily updating package.json versions and internal dependency pins to @webassemblyjs/* at version 1.13.4.

  • v1.13.3

    This release (v1.13.3) has no published release notes. The provided code diff shows no source code changes, only monorepo package metadata updates (version bumps in lerna.json and package.json files) plus corresponding internal dependency version upgrades across many @webassemblyjs packages.

  • v1.13.2

    Release v1.13.2 contains mostly internal parser support changes and a broad version bump across the monorepo packages. The only substantial code change shown is in wasm parsing of WebAssembly table element (elem) segments, plus additions for two WebAssembly memory instructions in the bytecode helper.

    Breaking
  • v1.13.1

    v1.13.1 does not include any release-note text (none provided), but the code diff shows a monorepo-wide version bump. Across 32 files, package versions and internal dependency pins were updated to 1.13.1, so consumers will pick up whatever behavioral changes exist in those updated subpackages.

  • v1.13.0

    v1.13.0 (release notes not provided by the publisher) adds WebAssembly reference types and table instruction support to the wasm bytecode decoding layer, and extends wasm-parser to recognize and decode those new opcode forms. It also tightens decoder error handling, adding explicit errors for unexpected value types and illegal bytecodes. Additionally, element segment decoding appears to have been updated to treat the leading field as a bitfield rather than a table index, which can change the resulting decoded program structure.

    BreakingFeatures
  • v1.12.1

    Release v1.12.1 has no publisher-provided release notes. The diff provided shows a monorepo-wide version synchronization to 1.12.1 across many packages, and updates internal dependencies to reference the new 1.12.1 versions.

  • v1.12.0

    This release (v1.12.0) contains a broad internal shift from Node.js Buffer usage to Uint8Array across byte-manipulation, LEB128, IEEE754 decoding, and parts of the WASM parser. It also extends the wasm-bytecode opcode symbol map with new extend8/extend16 signed variants. No release notes were provided, so the functional impact must be inferred from the code diff.

    Features
  • v1.11.4

    The publisher did not provide any release notes for v1.11.4, so the changes in this version are not documented in the provided material. Developers should review the corresponding code changes and commits between v1.11.3 and v1.11.4 to identify any undocumented behavior changes, bug fixes, or dependency updates.