WebAssembly / WebAssembly/component-model
Question: Linking components with Wasm modules
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 1.4k
- Forks
- 130
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 15
Description
As far as I see, this proposal describes components interacting with each other and the host.
How would linking components with a non-component Wasm module look like? Could we use some sort of "relaxed component format", where some of the imports/exports use component types while others use core WebAssembly?
For example: a browser app that shares memory and references with JS and DOM might want to use a component to implement some of its functionality.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the proposal referenced in the issue and the surrounding discussion about component-to-host interaction. Determine whether linking to a non-component WebAssembly module and mixing component and core WebAssembly imports or exports is specified. Done means producing an agreed design or documenting that the question remains unresolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100