wzprof

as far as I know wazero is the only zero-dependency Wasm runtime written in Go. This is not just one of those "written in $LANG" kinda deal: most other runtimes require linking against a native library; this in turn plays against a lot of the killer features of Go, such as good tooling, easy cross-compilation, goroutines [0]; so, not requiring Cgo means a team may bring wazero to their Go project without a second thought. As for other features, we may not be as bleeding edge as other projects, but we are a rather tiny team. If you expect support for WASI (preview 1) we have it :) we try to concentrate our effort on high-quality support of stable specs. EDIT: oh, and a huge shout-out to Stealthrocket, they are building a lot of cool stuff on top of wazero: - wzprof, a wasm profiler integrating with pprof https://github.com/stealthrocket/wz

Source-level debugging is what we have in mind; we have done a lot of work on Wazero and as part of https://github.com/stealthrocket/wzprof to enable it. It is still not a solved problem, and it requires support for each programming language that does things differently, but we're working towards this.

We are excited to present wzprof: a pprof-based profiler for WebAssembly modules. With it we can collect CPU and memory profiles during their execution. You execute your program compiled to WebAssembly under wzprof, and you get profiling metrics that can be consumed by anything that understands the pprof format (e.g. go pprof, Pyroscope, Parca). A few things motivated us to build this tool. WebAssembly runtimes typically allow profiling guest code via an external profiler such as perf, but in many cases, the recording and analysis of profiles remain a difficult task, especially due to features like JIT compilation. pprof is the de-facto standard profiling tool for Go programs and offers some of the simplest and quickest ways to gather insight into the performance of an application. wzprof aims the combine the capabilities and user experi