# pnpm "ERR_PNPM_UNEXPECTED_STORE" - Fix Store Path Mismatch in CI

> Fix pnpm "ERR_PNPM_UNEXPECTED_STORE: Unexpected store location" in CI - node_modules was created against a different store path than the current one. Reset the store or node_modules.

Source: https://latchkey.dev/learn/node-js/pnpm-err-pnpm-unexpected-store  
Updated: 2026-06-25

pnpm links node_modules from a content-addressable store and records which store path it used. ERR_PNPM_UNEXPECTED_STORE means the existing node_modules was built against a different store than the one pnpm now resolves - usually a cache or path change between runs.

## Diagnose it: reproduce the CI install locally

Install failures are usually environment drift rather than a broken lockfile: a different package-manager major, a different Node version, or a cache that is being restored from a run with different inputs. Reproduce the CI conditions before changing the lockfile, because regenerating it hides the real cause.

```Terminal
# match the runner exactly, then install from a clean slate
node --version && npm --version
rm -rf node_modules
npm ci --foreground-scripts

# if that succeeds locally but fails in CI, the difference is the cache
# or the package-manager version, not your lockfile
```

> Pin the package manager with Corepack (`"packageManager"` in package.json) so the runner and every developer machine resolve the same version. Version skew is the single most common source of lockfile errors that only appear in CI.

## Verify the fix survives a cold cache

A green run immediately after a fix often proves nothing, because it restored a cache written before the change. Force a cold install once to confirm the fix is real.

```.github/workflows/ci.yml
# temporarily bust the cache key to prove the fix on a cold runner
- uses: actions/setup-node@v4
  with:
    node-version: 22
    cache: npm
    cache-dependency-path: package-lock.json
# then bump this suffix once, run, and remove it
#   key: ${{ runner.os }}-node-${{ hashFiles('package-lock.json') }}-v2
```

## FAQ

### What causes pnpm "ERR_PNPM_UNEXPECTED_STORE"?

There are 2 common causes: node_modules restored from a different store path and the store path changed between runs. A cached node_modules built where the pnpm store sat at one path is restored on a runner whose store path differs (different HOME/user), so the recorded store no longer matches.

### How do I fix pnpm "ERR_PNPM_UNEXPECTED_STORE"?

There are 2 fixes depending on which cause you have: reset node_modules and pin the store path and cache the store, not node_modules. Work through them in order, since the first is the most common.

### What does pnpm "ERR_PNPM_UNEXPECTED_STORE" actually mean?

pnpm install aborts with ERR_PNPM_UNEXPECTED_STORE, reporting that node_modules was created with a different store location.

### How do I stop pnpm "ERR_PNPM_UNEXPECTED_STORE" happening again?

Pin store-dir to a stable path. The prevention section lists 3 changes that keep it from recurring.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt