Lockfiles & Build State
Elide keeps two binary files under .dev/ to make builds fast and incremental. Both are managed by Elide — you should not edit them by hand.
The two files
| File | Role |
|---|---|
.dev/elide.lock.v2.bin | Shared build state — the portable set of per-task input/output fingerprints, intended to be shareable across environments. |
.dev/elide.build.bin | Local build state — machine-local per-task fingerprints. |
elide build can skip tasks whose inputs have not changed; they differ only in scope (shared/portable vs. machine-local). Despite the lock in its name, .dev/elide.lock.v2.bin holds build-state fingerprints — not a resolved dependency graph. Both are written in a binary (Protocol Buffers) encoding.
> A separate resolved-dependency lockfile model exists in the codebase but is not currently written or read by the build (DefaultProjectLoader supplies no lockfile loader). Dependency-resolution state is instead recorded per ecosystem — for example npm's aube-lock.yaml — rather than in a unified lockfile.
Refreshing
elide install reuses cached resolution when the dependency list is unchanged. To ignore caches and re-resolve everything from scratch:
bash
elide install --fresh