Use wasm-tools to Investigate and Manipulate WebAssembly Artifacts
In this Shortcut, I’m going to introduce you to a more modern version of a toolchain for investigating and manipulating WebAssembly artifacts called wasm-tools. If you have been following along with the other Shortcuts in this playlist, you might a) be wary of learning about another set of tools, and b) wonder why I have switched to using the word “artifacts” instead of modules.
I can’t do much about that first reaction except to encourage you to keep an open mind because this trend will continue as we broaden our exploration of the larger WebAssembly ecosystem. And if you did have the second reaction, you are paying close attention! We are diverting from our existing mental models about how WebAssembly-based code is packaged and delivered in an exciting new direction. There is a lot to cover—more than will fit in several Shortcuts—so I’m going to continue to be deliberate and intentional about how I introduce new concepts, and I ask for your patience. You certainly do not have to read them in order, but if you come across a reference to something that does not make sense, I encourage you to go back and explore some of the previous Shortcuts for clarity.
Modules are not going anywhere, but with the expansion of WebAssembly use cases over time, the platform designers and engaged members of the user community started to find additional requirements. ...
Get Use wasm-tools to Investigate and Manipulate WebAssembly Artifacts now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
