Resolve the circular dependency between jco and componentize-js

[rajsite]

Currently there is a circular dependency between jco:

jco/packages/jco/package.json

Line 74 in 314b865

"@bytecodealliance/componentize-js": "^0.19.3",

And componentize-js:

https://github.com/bytecodealliance/ComponentizeJS/blob/ab6483f82ee47df4b0eab74a2533e24075fdbb83/package.json#L24

Haven't dug into it yet but curious if there are ideas on how to break the circular dependency (a new shared package potentially and where that would go) and if open to such a contribution.

[vados-cosmonic]

hey @rajsite this is a great point -- this is something we've wanted to do for a while but just hasn't been a high enough priority. We've made some moves in this direction though, so I'll reframe and lay out current progress below.

The circular dependency that exists between Jco comes down to dependency on the transpiled build of wasm-tools that is exported via jco's NPM package.

Thinking about this in the past, rather than moving this to another subproject (like jco-transpile), I wanted to start a completely different project for wasm-tools-in-Wasm. After some discussion in a JS meeting, we figured that it would be better to actually create that upstream as a direct output from the wasm-tools project:

bytecodealliance/wasm-tools#2374

So, right now if I were to lay out the steps to get rid of this interdependency, it would be:

1. Add codewasm-tools that encapsulates functionality for relevant tools (including the surface Jco needs) in Wasm
2. Add infra to wasm-tools to enable automatic publish of those Wasm binaries
3. Add an NPM package to jco named @bytecodealliance/wasm-tools that exports the transpiled modules that correspond to the usptream wasm outputs from wasm-tools
4. Use @bytecodealliance/wasm-tools from both jco and componentize-js

If all goes well, the the dependency graph would look like this:

graph TD;
    A(bytecodalliance/wasm-tools🦀) --wasm binaries--> B(bytecodealliance/wasm-tools ☕)
    B(bytecodealliance/wasm-tools ☕) --transpiled ES modules--> C(componentize-js ☕)
    B(bytecodealliance/wasm-tools ☕) --transpiled ES modules--> D(jco ☕)
    C --functionality--> D

Loading

☕ indicates an JS package above

With this, we should be able to remove the dependency on jco from ComponentizeJS