wasmparser
Advanced tools
Comparing version 3.1.0 to 3.1.1
@@ -0,1 +1,8 @@ | ||
## [3.1.1](https://github.com/wasdk/wasmparser/compare/v3.1.0...v3.1.1) (2020-08-19) | ||
### Bug Fixes | ||
* **threads:** add atomic.fence ([a9fd605](https://github.com/wasdk/wasmparser/commit/a9fd605d175fe91f4991321cd43d0db7868f01df)), closes [/github.com/WebAssembly/wabt/commit/d041025854ba2b00b3df9f308914c8aba05dcda9#diff-25d902c24283ab8cfbac54dfa101ad31](https://github.com//github.com/WebAssembly/wabt/commit/d041025854ba2b00b3df9f308914c8aba05dcda9/issues/diff-25d902c24283ab8cfbac54dfa101ad31) | ||
# [3.1.0](https://github.com/wasdk/wasmparser/compare/v3.0.0...v3.1.0) (2020-07-13) | ||
@@ -2,0 +9,0 @@ |
@@ -225,2 +225,3 @@ export declare const enum SectionCode { | ||
i64_atomic_wait = 65026, | ||
atomic_fence = 65027, | ||
i32_atomic_load = 65040, | ||
@@ -227,0 +228,0 @@ i64_atomic_load = 65041, |
@@ -225,2 +225,3 @@ export declare const enum SectionCode { | ||
i64_atomic_wait = 65026, | ||
atomic_fence = 65027, | ||
i32_atomic_load = 65040, | ||
@@ -227,0 +228,0 @@ i64_atomic_load = 65041, |
{ | ||
"name": "wasmparser", | ||
"version": "3.1.0", | ||
"version": "3.1.1", | ||
"description": "Binary WebAssembly file parser.", | ||
@@ -56,3 +56,3 @@ "main": "dist/cjs/index.js", | ||
"typescript": "^3.9.5", | ||
"wabt": "1.0.13" | ||
"wabt": "1.0.15" | ||
}, | ||
@@ -59,0 +59,0 @@ "dependencies": { |
@@ -25,4 +25,5 @@ [![Build Status](https://travis-ci.org/wasdk/wasmparser.svg?branch=master)](https://travis-ci.org/wasdk/wasmparser) | ||
### Creating Tests | ||
Place a `.wasm` and an associated `.wasm.out` file in the `test` directory. | ||
The testing harness will compare the parsing output of the `.wasm` file against the `.wasm.out` file. | ||
You can use the `npm test update` command to automatically create a `.out` files. This is useful if you have made a change that affects the tests. | ||
Test `.wasm` files are located in the `test/__fixtures__` directory. | ||
The testing harness compares the parsing output of the `.wasm` file against the snapshot file. | ||
You can use the `npm test -- --updateSnapshot` command to update the snapshot file. This is useful if you have made a change that affects the tests. |
Sorry, the diff of this file is too big to display
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is too big to display
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is too big to display
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
966124
18695
29