Stream: ComponentizeJS

Topic: StarlingMonkey Engine Release


view this post on Zulip Guy Bedford (Mar 21 2024 at 00:05):

ComponentizeJS 0.8.0 was just released on top of the StarlingMonkey engine - https://github.com/bytecodealliance/ComponentizeJS.

This is a huge step towards consolidation of JS on Wasm platform work, thanks to @Till Schneidereit's work in designing this extensible engine approach.

With a full event loop now supported, WASI stdio, random and clocks are enabled by default, and can instead be disabled by passing disableFeatures to the componentization process.

Feedback very welcome!

JS -> WebAssembly Component. Contribute to bytecodealliance/ComponentizeJS development by creating an account on GitHub.

view this post on Zulip Ramon Klass (Mar 21 2024 at 16:03):

great work :)

https://github.com/fermyon/StarlingMonkey/blob/main/tests/smoke.js#L162

is this way of implementing wasi:http/proxy supported by ComponentizeJs or is that a StarlingMonkey.wasm feature?

view this post on Zulip Kyle Gray (Apr 02 2024 at 19:57):

I have the same question. I'm trying to implement the http/proxy world and haven't figured out how to use fetch.

view this post on Zulip Kyle Gray (Apr 02 2024 at 21:33):

Opened up an issue with the error that I'm seeing https://github.com/bytecodealliance/ComponentizeJS/issues/96

Using the command-extended world, I'm trying to use fetch. The following code compiles to WASM but traps at runtime. // All of the same imports and exports available in the wasi:cli/command world /...

view this post on Zulip Till Schneidereit (Apr 04 2024 at 14:34):

hey Kyle, thank you for the report! I'm aware of a bunch of bugs in the fetch implementation in StarlingMonkey—and those are the reason why I haven't otherwise talked much about the project. I'm working through them right now, and will update the issue you opened once I resolved them


Last updated: Dec 23 2024 at 12:05 UTC