Is it safe to cache `output`?
Nobody has claimed this yet.
- Dominant language
- PureScript
- Stars
- 831
- Forks
- 137
- PR merge metrics
- No merged PRs in 30d
Description
My understanding is that Spago puts all build products into the output sub-directory. This includes both all the dependencies and the project code itself.
I would like to speed up continuous integration by caching this directory. Is it expected by design that exactly the updated code will be re-built in the presence of output filled with earlier build products?
Also, would newer versions of dependencies be downloaded and re-built automatically if such are available?
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.
Research direction
Start by tracing how Spago handles the output directory, dependency resolution, and CI reuse; the issue names no files or tests. Done means documenting whether cached products are safely reused and whether changed code and newer dependencies are rebuilt or fetched.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, tooling
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100