Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] Incremental building #416

Closed
chrisdmacrae opened this issue Feb 15, 2019 · 4 comments
Closed

[RFC] Incremental building #416

chrisdmacrae opened this issue Feb 15, 2019 · 4 comments

Comments

@chrisdmacrae
Copy link
Contributor

chrisdmacrae commented Feb 15, 2019

I would like to take a crack at incremental building in the next year.

Summary

As assets are processed during the initial build, we will build a dependency graph of the assets, building an abstract syntax tree of the build.

This will require us to do a few things:

  • Have a method for building an AST for a given template engine, extracting it's unique dependencies. (this is not easy)
  • extrapolate dependencies from pagination
  • extrapolate dependencies from data used in the page (this is not easy)
  • creating a temporary memory and filesystem cache to compare the contents of a source file against the last build
  • add the ability to trigger a rebuild of only specific files

This will allow for truly incremental building, by allowing us to:

  • track what the relationship between templates and data are
  • trigger rebuilds of only the changed template, and the pages that that template is referenced by
  • allow persisting this between dev and prod builds
@zachleat
Copy link
Member

zachleat commented Mar 9, 2019

Uh, wow—this would be quite a lot of work and a HUGE pull request. This would need to be pared down into individual issues before we move forward!

@zachleat
Copy link
Member

zachleat commented Mar 9, 2019

TemplateMap.js has some of this already in upcoming 0.7.2, but certainly not all of it.

@zachleat
Copy link
Member

zachleat commented Sep 7, 2019

This is a duplicate of #108. We should coalesce over there!

@pbuzdin
Copy link

pbuzdin commented Nov 18, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

3 participants