Incremental builds
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 20.8k
- Forks
- 2.3k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 156
Description
Describe the problem
I think it nice to have incremental builds similar to what Gatsby have https://support.gatsbyjs.com/hc/en-us/articles/360053099253-Gatsby-Builds-Full-Incremental-and-Cloud. It rebuilds only changed files. It can be big time saver for sites with a large number of pages.
Describe the proposed solution
Sveltekit rebuilds only changed files. As i understand, it must build dependency graph for all files in src/**.
Alternatives considered
No response
Importance
nice to have
Additional Information
No response
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 reading the linked Gatsby incremental-build description and tracing how SvelteKit currently builds files under src/**. Determine how changed files and their dependencies would be identified. Done means rebuilds process only affected files while preserving correct output for unchanged content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100