Skip to content

--incremental Build, only process files that have changed. #108

@zachleat

Description

@zachleat

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)
  • 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 an extend or an import or other internal-to-template-language specific feature, how do we discover what other files consume this? Maybe no way to tell for relative includes that don’t live in the includes folder?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions