Max Desiatov

WebAssembly hosts have certain limits placed on modules they load, and binaries not satisfying these limits don't pass validation, which hosts are required to do before actual execution. The Swift...

wasminspect is fantastic, and I much appreciate your work on that, we definitely should link to it as we improve user-visible documentation. I'm not sure though if it would work...

They've posted an update, and looks like it's fully working with Emscripten 🤔 https://developers.google.com/web/updates/2020/12/webassembly

I think adding breakpoints and stepping through source code is as good as it can get right now. The rest depends on browser implementors and how quickly the debugging format...

@jhoughjr does updating to JavaScriptKit 0.10.0 resolve the issue for you?

In the meantime, I've created https://github.com/bytecodealliance/wasm-micro-runtime/issues/482 to track this in WAMR proper.

I'm ok with either `swift package init --list-available-options` or `swift package init list-options`, although slightly biased towards the latter: it makes it impossible to specify ambiguous combinations like `swift package...

I hope JSON could also be supported that way, as that allows tools from other ecosystems to easily consume it.

Swift SDKs can be generated from existing toolchains. Thus we need an armv7 toolchain first (for some Linux distribution, Docker images could work too) to run the generator on it.

Feel free to submit a PR on [the corresponding repo](https://github.com/swiftlang/swift-sdk-generator), which already supports a few other distributions that you could use as an example.