ComponentizeJS
ComponentizeJS copied to clipboard
bytecodealliance
JS -> WebAssembly Component
Updates to the latest StarlingMonkey and Jco versions.
`componentize` should throw an error when it it builds a component without satisfying world exports.
As the title states, consider the the following case ``` // hello.wit package local:hello; world hello { export hello: func(name: string) -> string; } ``` ```js // hello.js // Intentionally...
When implementing sync component model functions as async exports in JS (functions returning a promise), we should integrate with the event loop by: * Detecting if a promise is returned...
I am attempting to use the engine produced by a debug build of the [PR](https://github.com/bytecodealliance/StarlingMonkey/pull/52) that refactors fetch. My understanding is that it should be sufficient to pass the `engine`...
Currently when the Wasm engine panics, it's impossible to figure out where in StarlingMonkey / ComponentizeJS the panic happened. For debugging these kinds of errors it would be much easier...
Hi, I'm getting a wizer error when trying to use jco. This is a continuation of troubleshooting of https://github.com/bytecodealliance/StarlingMonkey/issues/15#issuecomment-2350455813. In `jco/node_modules/@bytecodealliance/componentize-js/src/componentize.js`, I turned on debugging. ``` const DEBUG_BINDINGS = true;...
This refactoring makes a few changes to the code to make componentize-js a bit easier to debug: - enable passing debug options all together - enable passing where to output...
~~This PR is blocked on merge of upstream `orca` PR:~~ ~~https://github.com/thesuhas/orca/pull/241~~ ~~This PR is blocked on a newer release of `js-component-bindgen`~~ This PR updates the upstream ecosystem dependencies to *.227.1....
## Summary For certain scenarios, it would be great if we could create WebAssembly Components from JS/ESM with this library, without requiring a JS runtime. ## Background If a backend...
