You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am mainly thinking of introducing mini utils to inspect .wasm binaries for commonly useful features. One particular useful usage would be scanning exports for plugins (#2) and also detecting global imports.
It can be also exported as a CLI script and also utils.
Ideas welcome for util useful tools.
The text was updated successfully, but these errors were encountered:
Thanks dear @kazupon yes i am aware of this project. The goals of this tracker is to most importantly expose a nice JS API to inspect and work with .wasm format. For now we use wasm-parser that is excellent and pure JS. In the future for performance and more upstream compatibility, we might migrate to use wasm build of wasm-tools and expose bindings around it.
I am mainly thinking of introducing mini utils to inspect
.wasm
binaries for commonly useful features. One particular useful usage would be scanning exports for plugins (#2) and also detecting global imports.It can be also exported as a CLI script and also utils.
Ideas welcome for util useful tools.
The text was updated successfully, but these errors were encountered: