Mendy Berger (Jan 05 2026 at 19:22): 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?
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)
Mendy Berger (Jan 05 2026 at 19:47):That would be pretty bad, as ComponentizeJS relies on the NPM package
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 ;)
Victor Adossi (Jan 21 2026 at 16:07):@fitzgen (he/him) hey would you mind sharing how to do a release here for Wizer? We'd like to get the latest code out into NPM -- is it as easy as kicking off a GH action? (assuming of course one had the right creds!)
fitzgen (he/him) (Jan 21 2026 at 18:36):I don't really know how the npm publishing worked. Jake Champion and Guy Bedford were the ones who maintained the npm package and its CI publishing. They have both since stopped participating in the BA and we haven't had anyone step up to port that infrastructure to Wizer's new home inside the Wasmtime repo. I also am not really sure about the npm account credentials.
I think what is needed is someone to investigate what the old npm publishing scripts in CI did, port them to Wasmtime, and in the process figure out exactly what credentials and such are needed. And step up and take responsibility for maintaining this infrastructure over time.
Chris Fallin (Jan 21 2026 at 18:45):It looks like the npm package (https://www.npmjs.com/package/@bytecodealliance/wizer) is owned by Till, Victor and myself in addition to Guy. I'm happy to push a button to grant credentials whenever needed or transfer this to proper team ownership, though I also have zero remaining idea about how it worked and second the request for a new person to understand and own it
Victor Adossi (Jan 22 2026 at 09:08):Ah thanks for clarifying this for me y'all :bow:
With regards to your note @fitzgen (he/him)
we haven't had anyone step up to port that infrastructure to Wizer's new home inside the Wasmtime repo. I also am not really sure about the npm account credentials.
I can absolutely step up to get the publishing scripts in order and do this -- did not realize this was a gap at present. P3 Jco is my current focus but there's a lot of sort of backed up CI contributions that I have lower on my priority list so this probably fits in there somewhere.
With regards to what you noted @Chris Fallin
I'm happy to push a button to grant credentials whenever needed or transfer this to proper team ownership, though I also have zero remaining idea about how it worked and second the request for a new person to understand and own it
On the team ownership point @Bailey Hayes is probably a good CC here -- On the NPM side we should definitely have a bot account w/ credentials stored by the BA that is on all of the projects.
If you're suggesting that it really should be a completely new person to the process happy to go with that, but without any strong objections I'll try to work on this.
Bailey Hayes (Jan 22 2026 at 14:48):Yes, we have a bot user you can use. This user is also already configured for open vsx.
If the configured pat for this job is already valid and we can get something published now, let's do that first. Then come up with the best path for maintainable CI (should it just be a hook on wasmtime release? part of jco's release schedule? etc etc).
Victor Adossi (Jan 22 2026 at 15:06):Yeah I'm not sure what PAT is on the repo right now actually -- I'm not a maintainer on Wizer, so I can't do that release.
Since Wizer has essentially moved to wasmtime it looks like we should be moving the release process to be a part of wasmtime, and moving the Wizer code that is outside there into wasmtime...
Victor Adossi (Jan 22 2026 at 15:10):@fitzgen (he/him) / @Chris Fallin how do you want to proceed? It seems like we have two options:
@bytecodealliance/wizer as is, then do (2)@bytecodealliance/wizer's content into @bytecodealliance/wasmtime along with relevant, then do a releaseI'd like to do (1) then (2), but happy to go straight to (2) if anyone feels strongly about it.
Regardless, I'd need access to the Wizer repo as a maintainer to make that happen (I'm not a maintainer on the GH side).
Ramon Klass (Jan 22 2026 at 15:15):not to derail but I did upload https://github.com/Gentle/wizerjs now, but I don't think I have the time to maintain it alone, Victor are you interested? This is that wizer compiled to wasm code I mentioned
Chris Fallin (Jan 22 2026 at 17:54):If you're suggesting that it really should be a completely new person to the process happy to go with that, but without any strong objections I'll try to work on this.
no I'm happy to see you take this over @Victor Adossi -- thanks! By "new person" I just meant "not me or the other listed current owners" :-)
Victor Adossi (Jan 22 2026 at 18:09):Hahah OK! yeah I was wondering just a bit where a new person to get fully ramped up on this was going to come from! We've definitely got some contributors but the venn diagram of people who understand all the bits required is probably pretty unfortunately small at this point.
Alright well biasing for action here, if no one has any strong objections I'm going to go with the 1-2 here!
Release a version with the current repo (making any changes necessary), then get a PR in to wasmtime that moves the publishing mechanisms and any other necessary code over so that wasmtime can automatically ( :fingers_crossed: ) trigger releases as they move.
Last updated: Feb 24 2026 at 04:36 UTC