The first sentence of the readme file is:
wabt.js is a port of WABT to the Web, allowing you to manipulate WebAssembly modules using a JavaScript API.
I think you are stretching the meaning of "port" here.
In my mind "port" implies a reimplementation (here from C++ to TypeScript).
And I am looking for a reimplementation of the wabt tools,
since the GC proposal isn't supported by the wat2wasm.
(See issue WebAssembly/wabt#2530 )
Seeing that you have an --enable-gc I thought I had found an alternative,
but digging further, I understand that you are compiling the standard wabt tools with emscripten
and then providing an interface to it.
Proposal: Make it clear in the readme that wabt.js is a layer on top of the original wabt tools.
(I understand that you are using "port" in the sense "now runs on another platform").
Btw - consider removing the --enable-gc option.
It's confusing that enabling has no effect.
The first sentence of the readme file is:
I think you are stretching the meaning of "port" here.
In my mind "port" implies a reimplementation (here from C++ to TypeScript).
And I am looking for a reimplementation of the wabt tools,
since the GC proposal isn't supported by the
wat2wasm.(See issue WebAssembly/wabt#2530 )
Seeing that you have an
--enable-gcI thought I had found an alternative,but digging further, I understand that you are compiling the standard wabt tools with emscripten
and then providing an interface to it.
Proposal: Make it clear in the readme that wabt.js is a layer on top of the original wabt tools.
(I understand that you are using "port" in the sense "now runs on another platform").
Btw - consider removing the
--enable-gcoption.It's confusing that enabling has no effect.