Cached dependencies for faster builds

Build sandboxes now reuse preloaded images and a shared node_modules cache, so dependency installs take less wall time on each push.

What gets reused

Easel keeps warm sandbox images with common tooling already present. Across builds, a shared dependency cache stores installed packages so unchanged lockfile inputs can skip a full cold install.

When package-lock.json, pnpm-lock.yaml, or yarn.lock changes, the cache refreshes for the affected tree. Unchanged deps continue to hit.

What you do

Nothing special for most apps: push as usual and watch install phases shorten in build logs. Monorepos with stable lockfiles see the largest gains because most packages stay cacheable between deploys.

Pair this with Enhanced build machines or Turborepo remote cache when you need more CPU and task-level reuse on top of install caching.