bytecodealliance / bytecodealliance/ComponentizeJS
Support OCI annotations custom metadata tool convention.
- Dominant language
- Rust
- Stars
- 391
- Forks
- 53
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 1
Description
Similar to what [cargo-component does](https://github.com/bytecodealliance/cargo-component/pull/372), we want components produced by guest toolchains to adhere to this (not yet merged/accepted but in practiced used) tool convention: https://github.com/WebAssembly/tool-conventions/pull/248
Refer to wasm-metadata's [oci_annotations](https://github.com/bytecodealliance/wasm-tools/tree/main/crates/wasm-metadata/src/oci_annotations) module.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the wasm-metadata oci_annotations module and the linked cargo-component change, then compare the tool-conventions proposal with how ComponentizeJS currently produces components. Done means guest-toolchain components follow the referenced OCI annotation convention; the issue names no ComponentizeJS files or tests, so those must be located first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100