Repeatable Gatsby dev environment with Node pinning and lockfiles

A team wants a repeatable Gatsby development environment across machines using Node version pinning and a committed dependency lockfile.

The project relies on Gatsby's generated .cache and public directories which are typically gitignored and regenerated on clone. Incremental builds and cache reuse improve speed but add statefulness. The unified GraphQL schema is built from source plugins and local files, and image processing can be affected by file system timestamps and OS differences.

With Node version pinned via .nvmrc or package.json engines and lockfile committed, which build artifacts remain nondeterministic across machines? Does incremental cache state create divergence risk when .cache is not shared? Which outputs should be considered non-reproducible by design?