10 Commits

Author	SHA1	Message	Date
Alexander Akait	17b9d03f27	fix: a lot of types	2025-04-07 16:09:05 +03:00
alexander-akait	70bdb248e4	fix: no `Function` types	2025-03-13 19:34:04 +03:00
daxpedda	d5dc65eedd	Accept `externref` as valid type to interact with	2024-11-14 15:40:37 +01:00
alexander.akait	3e3dfd781b	fix(types): more	2024-03-17 20:15:44 +03:00
alexander.akait	568f28bb87	refactor(types): more	2023-06-14 19:45:51 +03:00
alexander.akait	3591783d9e	refactor(types): wasm and runtime	2023-05-26 01:18:44 +03:00
Liam Murphy	a74f64e891	Add `i64` to the set of JS-compatible wasm types in `syncWebAssembly` mode ... For quite a while now, it's been possible for WebAssembly `i64`s to be converted to/from JS bigints (as function parameters, results, etc.). However, `syncWebAssembly` mode currently rejects any modules that attempt to do so, because `i64` isn't in it's list of JS-compatible types. This fixes that by adding `i64` to that list. There was an existing test that used `i64` as an example of a non-JS-compatible type; I replaced that with `v128`.	2022-10-06 20:36:48 +11:00
Tobias Koppers	b0fa9ccada	pretty files	2021-05-11 09:31:46 +02:00
Tobias Koppers	4f963aa03f	update `@webassemblyjs`	2021-01-09 10:39:24 +01:00
Tobias Koppers	aa67a435a4	refactor wasm loading from target into output.wasmLoading option ... allow entry specific wasm loading	2020-09-09 11:20:37 +02:00