ComponentizeJS
ComponentizeJS copied to clipboard
bytecodealliance
JS -> WebAssembly Component
In https://github.com/bytecodealliance/jco/pull/262, we now validate all borrows properly. The need to call `resource[Symbol.dispose]()` explicitly for all functions that take resources seems unnecessary though. Rather, the implementation should always auto-drop borrows...
I'm getting the error `source.js:2:43 SyntaxError: ambiguous indirect export: MyEnum` when I try to import my enum like: `import { MyEnum } from 'my_package:my_world/my_module'` -- I see in debug mode...
**Problem** The size of wasm module produced is quite high, ~ 8 MB for a function adding two numbers. My understanding is that the interpreter (SpiderMonkey) is the majority of...
Brought up at CTW - Spidermonkey has a debugger API that we should figure out the right integration for. Unfortunately it does not include a debugging protocol itself, so one...
One of the trickiest parts of a ComponentizeJS workflow is figuring out the write structure to author the code to. We should generate the boilerplate outline for the world being...
Say I have a js library that is already using an emscripten generated wasm file and I try to componentize that, given spider monkey supports wasm, can I "just" bundle...
When using say a restricted error variant, throwing an unsupported error will be masked by the "invalid variant" error in the bindings. In componentize bindings, we should specially handle invalid...
We should automatically support a TypeScript input and also having dependencies being bundled in as well, down to imports not colliding with the world imports.
`console` logging should be going through wasi-logging, either by default or as an option.
The current GC strategy is to just clear all allocations at the end of each call, but we need to allow the JS ArrayBuffers to hold on to the memory...