Daniel Macovei

> We talked about this a bit in the TSC meeting today, since it touches on interesting aspects for Bytecode Alliance hosted activities. What we realized is that we think...

Would love to do that. Will try and get a PR up soon.

will bump to use a released version of wasm-pkg-tools after https://github.com/bytecodealliance/wasm-pkg-tools/pull/124 is merged

Also happy to help out with this. I helped a bit with some of the more recent changes for multi-package WIT stuff. I wouldn't be surprised if there are additional...

Also looking again, I'm curious if the example was written before or after [this change](https://github.com/WebAssembly/component-model/pull/380). It looks like this example may not have a root package declaration, which is required...

So if I'm following correctly then for the scope of this PR, since mixed package declaration styles isn't yet supported, then in Alex's example where we have: ``` package a:b1...

So I have implemented these changes locally for encoding multiple wit packages. When decoding though, I found that some modifications will be have to made [here](https://github.com/bytecodealliance/wasm-tools/blob/main/crates/wit-parser/src/decoding.rs#L148) as the current tooling...

After some more thought... I'll actually probably investigate refactoring [ComponentInfo](https://github.com/bytecodealliance/wasm-tools/blob/main/crates/wit-parser/src/decoding.rs#L47) into `ComponentsInfo`, with multiple packages in it. Then we could perform the existing check on each package, and it could...

Cool. I think I've essentially accomplished the thrust of what's involved in order to do to that now (locally)... As I'm tidying it up before requesting additional review, I'll be...

Hmm seems I botched something up switching branches... should be able to look into what went wrong shortly...