ComponentizeJS
ComponentizeJS copied to clipboard
bytecodealliance
JS -> WebAssembly Component
Right now, code that uses imports via WASI look like regular imports, with the package name being the first indicator: ```js import { someFn } from "ns:pkg/[email protected]"; export const run...
It would be great if `componentize-js` (or possibly one level lower at StarlingMonkey) could expose a platform detection mechanism JS that is used for components to rely upon. This would...
I'm attempting to build some code using the [pdfkit](https://www.npmjs.com/package/pdfkit) library and after replacing any APIs that are not currently supported I'm met with the following error: ``` Exception while evaluating...
During a recent PR that patched a bug in feature-based WASI interface stubbing, the point of how to deal with outgoing-handler came up: https://github.com/bytecodealliance/ComponentizeJS/pull/268#discussion_r2223776655 It *seems* like there are at...
We should add testing that checks for *pure* components - ensuring that components *without* all the "extra" exports/imports of StarlingMonkey can be built. This would be essentially a regression test...
As came up in a previous PR, it would be good to write Wizer ENV to a file along with other debug output, given the new expanded `debug` options that...