Gatsby Incremental Builds Land on Netlify

An incremental build is a simple idea in theory: with a generator that produces every file a site is made of, each build only updates the files that have changed since the last one instead of regenerating all of them. Whether that is workable in practice is another matter, because it is far from obvious how anything could know which files will change and which will not before the build even runs.

Gatsby has apparently worked this one out, per its page-build optimizations documentation. The payoff shows up in two places: local builds finish faster, and deployment speeds up as well, since far fewer files have to be moved around.

Incremental builds are a pretty big deal, and it is satisfying to watch this class of Jamstack problem get cleared away. Running this on Netlify takes one extra step: the company's build plugins feature has to be enabled first. That feature is itself worth a look, since it lets you execute code at different stages of CI/CD with a clean syntax.

For the full walkthrough, see the Netlify blog post on enabling Gatsby incremental builds on Netlify.