spinframework / spinframework/spin
Should `spin build` perform component dependency composition?
@fibonacci1729 is already working on this.
Since Apr 17, 2025.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
Currently when running spin build we do not perform component dependency composition. This means that developers won't know about issues with dependencies until they actually go to run the app. Ideally, we would give that feedback earlier.
On the flip side, the cost of component dependency composition is not trivial, and doing that composition to only just through that result away and do it again at load time is a bit wasteful. Would this lead us to think about storing the result of composition in some cache so that we don't necessarily have to do the composition at load time?
Contributor guide
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.
Assessment
This issue has not been assessed yet.