Stream: general

Topic: Publishing Wizer


view this post on Zulip Mendy Berger (Jan 05 2026 at 19:22):

I need to use the new Wizer that internally uses the newer wasmtime based Wizer.
I need the NPM version, so can't just rely on wasmtime wizer

Is there anything blocking the latest version from being published?

This commit is a follow-up to the merging of the Wizer repository into Wasmtime. At this time I don't have plans for what to do about the npm package or the old wizer CLI, so I've updated t...

view this post on Zulip Ramon Klass (Jan 05 2026 at 19:46):

I figure that if other folks are interested to maintain this then this is a reasonable-enough starting point and can take it from here.

I read this as "there is no maintainer currently", I also wanted to ask how to proceed with wizer since I'm using exnref in my code so the released one is not recent enough for me either (exnref does work though, it'd just be a new parameter like bulk-memory support, I have a patch)

view this post on Zulip Mendy Berger (Jan 05 2026 at 19:47):

That would be pretty bad, as ComponentizeJS relies on the NPM package

view this post on Zulip Ramon Klass (Jan 05 2026 at 19:53):

an interesting experiment I am working on is actually combining wasmtime-wizer with js WebAssembly.Instance, Alex recently refactored wizer so that any wasm runtime can be used and the special code can be compiled to wasm itself, so I have compiled wizer with wasm-bindgen, I just found another bug I need to fix but will upload to github later today or tomorrow

once this fully works, componentizejs could get a wizer version that is a 1MB wasm blob which otherwise uses js wasm during preinitialization, but then we really need to talk about who maintains what where ;)


Last updated: Jan 10 2026 at 20:04 UTC