Support new ComponentizeJS parameter for debug build

[alexcasalboni]

Since 0.17.0, ComponentizeJS supports a new debugBuild parameter (or --use-debug-build via CLI) for debugging Wasm stacks.

Would it make sense to expose that via jco as well?

If that's the case, happy to contribute myself :)

This is not really a blocker since you can easily use npx @bytecodealliance/componentize-js instead of npx @bytecodealliance/jco componentize. But I'd guess most people use ComponentizeJS via jco and they woudn't even realize there's a new debug parameter if not documented in this repo.

[vados-cosmonic]

Hey @alexcasalboni sorry for the delay here!

Would have loved to have your contribution of this feature (feel free to send a PR after creating the issue in the future!) -- @pchickey got to it first in #633 and is now available in the most recent release of jco (1.11.2).

Please try it out and let me know, happy to re-open this issue if it doesn't fit your needs.

This is not really a blocker since you can easily use npx @bytecodealliance/componentize-js instead of npx @bytecodealliance/jco componentize. But I'd guess most people use ComponentizeJS via jco and they woudn't even realize there's a new debug parameter if not documented in this repo.

You're absolutely right -- componentize-js is build mainly as a direct route to the compnentization features and we merely wrap and redistribute that functionality. jco aims to be a complete tool and add the ability to transpile components.

That said, documentation was certainly lagging, thanks for pointing out the lapse!