Socket
Socket
Sign inDemoInstall

wasmparser

Package Overview
Dependencies
1
Maintainers
3
Versions
99
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install
Previous1
35
10Next

2.2.0

Diff

Changelog

Source

2.2.0 (2020-06-10)

Features

  • add support for inline export notation (c730a88), closes #56
yurydelendik
published 2.1.0 •

Changelog

Source

2.1.0 (2020-06-10)

Features

  • use abbreviated syntax for all imports (39ee77c), closes #56
yurydelendik
published 2.0.0 •

Changelog

Source

2.0.0 (2020-06-10)

Bug Fixes

  • print data section entries in a single line (e2aa667)

Features

  • remove type section from disassembly (d61d67d), closes #56

BREAKING CHANGES

  • Disassembly output will no longer print all the types in the beginning by default.

The type section can be reconstructed from the implicit type information in the remainder of the disassembly, and is generally just cognitive overhead for developers, especially in the browser DevTools (see https://crbug.com/1092763 for relevant downstream issue in Chromium DevTools). Relying on the implicit type information is far more readable for humans and also avoids the need to dump all the types in the beginning, which take up precious space since both Chromium and Firefox DevTools limit the number of lines that are displayed for large Wasm modules.

This adds a skipTypes option to WasmDisassembler instances, which can be used to restore the old behavior. By default this option is set to true.

This includes a fix to call_indirect and return_call_indirect, where we had previously refered to the type by name, and now we use the abbreviated form for printing types as well [1].

yurydelendik
published 1.0.0 •

Changelog

Source

2.0.0 (2020-06-10)

Bug Fixes

  • print data section entries in a single line (e2aa667)

Features

  • remove type section from disassembly (d61d67d), closes #56

BREAKING CHANGES

  • Disassembly output will no longer print all the types in the beginning by default.

The type section can be reconstructed from the implicit type information in the remainder of the disassembly, and is generally just cognitive overhead for developers, especially in the browser DevTools (see https://crbug.com/1092763 for relevant downstream issue in Chromium DevTools). Relying on the implicit type information is far more readable for humans and also avoids the need to dump all the types in the beginning, which take up precious space since both Chromium and Firefox DevTools limit the number of lines that are displayed for large Wasm modules.

This adds a skipTypes option to WasmDisassembler instances, which can be used to restore the old behavior. By default this option is set to true.

This includes a fix to call_indirect and return_call_indirect, where we had previously refered to the type by name, and now we use the abbreviated form for printing types as well [1].

yurydelendik
published 0.16.1 •

yurydelendik
published 0.16.0 •

yurydelendik
published 0.15.0 •

yurydelendik
published 0.14.1 •

yurydelendik
published 0.14.0 •

yurydelendik
published 0.12.1 •

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc