-
-
Notifications
You must be signed in to change notification settings - Fork 550
Closed
Labels
enhancementfavoriteVanity label! We like this enhancement request a lot.Vanity label! We like this enhancement request a lot.feature: 🥝 incremental buildslarge-task
Milestone
Description
This is the step that requires knowledge of each template’s dependencies:
- What collections the changed template is a part of and what other templates consume those collections.
- Keep in mind JavaScript dependencies (for
11ty.js
) - If the file is a layout, rebuild other templates use the layout.
- If the file is a data file, rebuild what templates use the data (global data will require some extra work but directory and template data are straightforward)
- Stretch goal here for huge pagination templates is that it would be super nice to know what changed in the data file to have a bit more precision about what pagination templates we need to write. (Selfishly I want this for my twitter archive project) (Filed separately at Incremental Builds stretch goal: incremental pagination data sets #1087)
- Passthrough copy files filed separately as Incremental passthrough copy #977
Punt into separate issues, later:
- If the file is a config file, package.json, rebuild everything for now.
- If the file is an
include
or anextend
or animport
or other internal-to-template-language specific feature, how do we discover what other files consume this? Maybe no way to tell forrelative
includes that don’t live in the includes folder?
paulrobertlloyd, zachleat, jdsteinbach, levimcg, DirtyF and 234 morexplosionmindxplosionmindtejesh0, DanielTamkin, icdindia, santicros, advaiyalad and 1 more
Metadata
Metadata
Assignees
Labels
enhancementfavoriteVanity label! We like this enhancement request a lot.Vanity label! We like this enhancement request a lot.feature: 🥝 incremental buildslarge-task