ComponentizeJS 0.18.3 · ComponentizeJS

It took a lot of RCs to get here but at least the release process is now thoroughly automated (with the exception of one changelog generation issue with RCs).

@bytecodealliance/componentize-js

ESM -> WebAssembly Component creator, via a SpiderMonkey JS engine embedding. Latest version: 0.18.3, last published: 22 minutes ago. Start using @bytecodealliance/componentize-js in your project by running `npm i @bytecodealliance/componentize-js`. There are 6 other projects in the npm registry using @bytecodealliance/componentize-js.

Release 0.18.3 · bytecodealliance/ComponentizeJS

Changelog [0.18.3] - 2025-07-16 🚀 Features (ci) add release automation (#226) by @vados-cosmonic in #226 🐛 Bug Fixes allow for use of both manual & fetchEvent based HTTP (#247) by @vados-cosmon...

Fix CHANGELOG generation in the presence of RCs · Issue #258 · bytecodealliance/ComponentizeJS

Right now, when generating/updating the CHANGELOG for a release, only the commits up until the latest tag are included. This generally works for going from a release tag to a release tag (ex. 0.1.0...

Tomasz Andrzejak (Jul 16 2025 at 16:38):

Thank you Victor, this is great! Does this release bumps StarlingMonkey revision? If not, it might be maybe worth to make another release that updates StarlingMonkey which should fix implicit dependency on wasi/environement issue: https://github.com/bytecodealliance/ComponentizeJS/issues/194

Latest version seems to depend on `wasi:cli/environment@0.2.3` · Issue #194 · bytecodealliance/ComponentizeJS

With the release of ComponentizeJS v0.17.0 we seem to have a hard dependency on the target world wit importing wasi:cli.environment@0.2.3. This seems to be due to StarlingMonkey trying to call envi...

Victor Adossi (Jul 16 2025 at 16:51):

Hey Tomasz -- nope this version does not bump starling monkey -- it would be great if there were some releases to go by though, I actually didn't know that issue got fixed, there wasn't an update in that issue.

That said, if you could comment in there and confirm it's fixed I can definitely get to that next

Releases · bytecodealliance/StarlingMonkey

The StarlingMonkey JS runtime. Contribute to bytecodealliance/StarlingMonkey development by creating an account on GitHub.

Tomasz Andrzejak (Jul 16 2025 at 17:02):

Add an automated release process · Issue #95 · bytecodealliance/StarlingMonkey

Currently, StarlingMonkey doesn't contain an automated process to release binaries. This is something we should change, such that every merged PR results in a release including binaries for all of ...

Victor Adossi (Jul 16 2025 at 17:06):

Yeah I think just tagging releases would actually work to start! It doesn't have to be complicated at first, IIRC GH will pick up even just a simple tag and plenty of projects just manually click the release creation buttons in GH

Victor Adossi (Jul 21 2025 at 17:36):

Should have a release of ComponentizeJS out by tomorrow! Going through the RC right now

chore: update StarlingMonkey to commit 1f6f81f by vados-cosmonic · Pull Request #260 · bytecodealliance/ComponentizeJS

We read every piece of feedback, and take your input very seriously.

Victor Adossi (Jul 21 2025 at 18:13):

@bytecodealliance/componentize-js

ESM -> WebAssembly Component creator, via a SpiderMonkey JS engine embedding. Latest version: 0.18.3, last published: 5 days ago. Start using @bytecodealliance/componentize-js in your project by running `npm i @bytecodealliance/componentize-js`. There are 6 other projects in the npm registry using @bytecodealliance/componentize-js.

Tomasz Andrzejak (Jul 22 2025 at 09:46):

I'm not sure why I cannot assign you as reviewer but feel free to comment whenever you find a moment.

Stream: ComponentizeJS

Topic: ComponentizeJS 0.18.3