component-docs
component-docs copied to clipboard
Documentation around creating and using WebAssembly Components
Running the js component, created following [this section](https://component-model.bytecodealliance.org/language-support/javascript.html) of the guide, from the [example host](https://github.com/bytecodealliance/component-docs/tree/main/component-model/examples/example-host) no longer works. I guess because it's missing some wasi bits. ```sh Error: Failed to...
While doing the composition tutorial: I run the last command: ``` wac compose composition.wac -o final.wasm ``` And get: ``` error: failed to resolve document × failed to create registry...
In #149 `Note:` comments were made consistent as just comment blocks. In discussion https://github.com/bytecodealliance/component-docs/pull/149#issuecomment-2316155910 the idea was proposed to improve in the future. Found the [mdbook-alerts](https://crates.io/crates/mdbook-alerts) crate which adds support...
Let's try mentioned example for use with string, that's absolute straightforward. Component compiles well, but issuing `wasm-tools component wit target/wasm32-wasip1/release/adder.wasm` command produce really big file filled with a lot of...
Currently, new users must clone the `component-docs` repo, head to a specific sub-directory *then* attempt to build projects. It would be ideal if there were easier ways to download and...
Currently the Rust example often uses the same name for packages, functions, worlds, interfaces. (This might also be the case elsewhere in the book, not sure) Example: https://github.com/bytecodealliance/component-docs/blob/31445f3501113075c4a31c6aee426b8f75933a78/component-model/src/language-support/rust.md?plain=1#L82-L92 Here the...
This commit updates the language guide for JS Resolves #250 Resolves #199
It should be possible to publish a WIT interface from the `component-docs` repo automatically when a certain CI workflow is run. This *will likely* require the following: 1. Adding `bytecodealliance/component-docs`...
This issue arguably shouldn't go here, but currently UX issues in upstream tooling is making the Rust The goal is to revert [this reverted functionality](https://github.com/bytecodealliance/component-docs/pull/254) -- we *want* to be...
We should document resource usage in Javascript, or at least point to a place where the documentation can be found. At *this* point the information shouldn't change too much, but...