jco icon indicating copy to clipboard operation
jco copied to clipboard

JavaScript tooling for working with WebAssembly Components

Results 100 jco issues
Sort by recently updated
recently updated
newest added

Based on discussion in https://github.com/bytecodealliance/jco/issues/375.

Since Jco exposes the wasm-tools APIs, it would be nice for the browser build of Jco to also expose these APIs properly.

It would be beneficial to have a complete reference documentation for how WIT types are represented in JS, covering all WIT generations. While this will still evolve a little over...

Jco has prioritised correctness over performance. As adoption grows, we will need to investigate performance more carefully, both for code generation and for host call overhead. The first step here...

Now that source phase imports are at phase 3 we can consider what it would look like to output for this target. In addition this would also unlock cloudflare worker...

I've just encountered this error message in Chrome: ``` bundle.js:487 Uncaught RangeError: WebAssembly.Instance is disallowed on the main thread, if the buffer size is larger than 8MB. Use WebAssembly.instantiate, or...

We should be stricter about traps in jco. When a component traps it moves into a trapped state and is no longer callable, so this should be a flagged state...

enhancement

This issue is intended for tracking adding a shim for wasi-nn. Tasks: - [ ] ... - [ ] ...

I noticed in making [this little demo](https://github.com/bytecodealliance/component-docs/tree/main/component-model/examples/tutorial/jco) that I could _not_ use signed or out-of-bounds numbers for `wasmtime` but that in the browser and via node it does. https://stackoverflow.com/help/minimal-reproducible-example adding...

While debugging the `jco` preview2-shim unit tests under `deno` I stumbled over another grave compatibility issue. It's more or less hidden when executed on `nodejs`, but has its roots in...

target-deno