Where Does Parcel Store Its Build Cache?
Parcel caches builds in .parcel-cache inside your project. What it holds, the --cache-dir move, and why --no-cache still writes.
Last updated
Parcel caches everything it builds to disk, so restarts only rebuild changed files with their configs and plugins. The cache lives in .parcel-cache at the project root. It is keyed to your exact code state, which is why committing it causes phantom diffs and stale teammates.
Override the spot with --cache-dir for RAM disks or shared CI paths. Note the trap: --no-cache only skips reading, while the folder still gets written. Parcel v1 used node_modules/.cache/parcel instead, so check the version when an old guide's path doesn't exist.
Where Parcel stores this, by platform
.parcel-cache
Inside the project root. Gitignore it always. Move it per run with parcel build --cache-dir D:\fast-cache. Deleting it is the first fix for builds that ignore source changes.
.parcel-cache
Same project-relative role. Config changes invalidate dependents granularly, so most staleness traces to a plugin version bump instead. Wipe and rebuild to confirm.
.parcel-cache
Mirrors macOS. Docker builds should exclude it via .dockerignore or mount it as a named volume for warm CI caches.
Frequently asked questions
Should I commit .parcel-cache to git?
No. Add it to .gitignore. The cache is machine-specific and regenerates on every build. Committing it bloats history and risks teammates restoring entries that no longer match their code.
Parcel ignores my changes, what do I delete?
Remove .parcel-cache at the project root and rebuild. If ghosts persist, verify the config file Parcel actually loads, since granular invalidation keys off configs and plugins it tracks.
Notice an outdated path? Let us know.