Build fails with `File exists: /Users/expo/.nvm/versions/node/v20.18.0/bin/pnpm`

### Build/Submit details page URL

https://expo.dev/accounts/pokey.rule/projects/flashcards/builds/3ddcb3d5-2455-44f2-abfa-84af13e0f4c1

### Summary

I get an error in the eas cloud build when I configure my `eas.json` to use `corepack` for my `pnpm` project

```console
Installing node v20.18.0
Downloading and installing node v20.18.0...
Downloading http://10.94.183.70:8081/v20.18.0/node-v20.18.0-darwin-arm64.tar.xz...
########################################################################
100.0%
Computing checksum with sha256sum
Checksums matched!
Now using node v20.18.0 (npm v10.8.2)
default -> 20.18.0 (-> v20.18.0 *)
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated npmlog@4.1.2: This package is no longer supported.
npm warn deprecated are-we-there-yet@1.1.7: This package is no longer supported.
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated gauge@2.7.4: This package is no longer supported.
added 144 packages in 15s
12 packages are looking for funding
run `npm fund` for details
Enabling corepack
Installing pnpm@9.15.9
npm error code EEXIST
npm error path /Users/expo/.nvm/versions/node/v20.18.0/bin/pnpx
npm error EEXIST: file already exists
npm error File exists: /Users/expo/.nvm/versions/node/v20.18.0/bin/pnpx
npm error Remove the existing file and try again, or run npm
npm error with --force to overwrite files recklessly.
npm error A complete log of this run can be found in: /Users/expo/.npm/_logs/2025-08-02T18_29_42_277Z-debug-0.log
Failed to install pnpm 9.15.9

Error: Failed to install pnpm. Make sure you specified the correct version in eas.json.
```

### Managed or bare?

Managed

### Environment

```console
➜ npx expo-env-info
Need to install the following packages:
expo-env-info@1.3.4
Ok to proceed? (y)

expo-env-info 1.3.4 environment info:
System:
OS: macOS 15.4
Shell: 5.9 - /usr/local/bin/zsh
Binaries:
Node: 20.18.0 - ~/.asdf/installs/nodejs/20.18.0/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 10.8.2 - ~/.asdf/plugins/nodejs/shims/npm
Watchman: 2025.05.26.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.16.2 - /usr/local/opt/ruby/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 24.5, iOS 18.5, macOS 15.5, tvOS 18.5, visionOS 2.5, watchOS 11.5
Android SDK:
System Images: android-30 | Intel x86_64 Atom
IDEs:
Android Studio: 2024.3 AI-243.26053.27.2432.13536105
Xcode: 16.4/16F6 - /usr/bin/xcodebuild
npmPackages:
expo: ~53.0.11 => 53.0.11
expo-router: ~5.1.0 => 5.1.0
expo-updates: ~0.28.14 => 0.28.14
react: 19.0.0 => 19.0.0
react-dom: 19.0.0 => 19.0.0
react-native: 0.79.3 => 0.79.3
npmGlobalPackages:
eas-cli: 16.17.4
Expo Workflow: bare

➜ npx expo-doctor
env: load .env.local
env: export EXPO_PUBLIC_MODE
11/15 checks passed. 4 checks failed. Possible issues detected:
Use the --verbose flag to see more details about passed checks.

✖ Check dependencies for packages that should not be installed directly
The package "expo-modules-autolinking" should not be installed directly in your project. It is a dependency of other Expo packages, which will install it automatically as needed.
Advice:
Remove these packages from your package.json.

✖ Check that native modules use compatible support package versions for installed Expo SDK
Expected package @expo/config-plugins@~10.1.1
Found invalid:
@expo/config-plugins@10.0.2
@expo/config-plugins@10.0.2
@expo/config-plugins@10.0.2
@expo/config-plugins@10.0.2
@expo/config-plugins@10.0.2
@expo/config-plugins@10.0.2
@expo/config-plugins@10.0.2
(for more info, run: npm why @expo/config-plugins)
Advice:
Upgrade dependencies that are using the invalid package versions.

✖ Validate packages against React Native Directory package metadata
The following issues were found when validating your dependencies against React Native Directory:
Untested on New Architecture: immer
No metadata available: immutability-helper, jstat, loglevel, mersenne-twister, mobx, mobx-react-lite, mobx-state-tree, ramda, react-use, serializr
Advice:
Use libraries that are actively maintained and support the New Architecture. Find alternative libraries with https://reactnative.directory.
Add packages to expo.doctor.reactNativeDirectoryCheck.exclude in package.json to selectively skip validations, if the warning is not relevant.
Update React Native Directory to include metadata for unknown packages. Alternatively, set expo.doctor.reactNativeDirectoryCheck.listUnknownPackages in package.json to false to skip warnings about packages with no metadata, if the warning is not relevant.

✖ Check that packages match versions required by installed Expo SDK
The following packages should be updated for best compatibility with the installed expo version:
expo@53.0.11 - expected version: 53.0.20
expo-application@6.1.4 - expected version: ~6.1.5
expo-build-properties@0.14.6 - expected version: ~0.14.8
expo-constants@17.1.6 - expected version: ~17.1.7
expo-dev-client@5.2.0 - expected version: ~5.2.4
expo-file-system@18.1.10 - expected version: ~18.1.11
expo-font@13.3.1 - expected version: ~13.3.2
expo-image@2.3.0 - expected version: ~2.4.0
expo-linking@7.1.5 - expected version: ~7.1.7
expo-router@5.1.0 - expected version: ~5.1.4
expo-splash-screen@0.30.9 - expected version: ~0.30.10
expo-system-ui@5.0.8 - expected version: ~5.0.10
expo-updates@0.28.14 - expected version: ~0.28.17
expo-web-browser@14.1.6 - expected version: ~14.2.0
react-native@0.79.3 - expected version: 0.79.5
jest-expo@53.0.7 - expected version: ~53.0.9
Your project may not work correctly until you install the expected versions of the packages.
Found outdated dependencies
Advice:
Use 'npx expo install --check' to review and upgrade your dependencies.

4 checks failed, indicating possible issues with the project.
```

### Error output

_No response_

### Reproducible demo or steps to reproduce from a blank project

here is my `eas.json`:

```json
{
"cli": {
"version": ">= 16.6.1",
"appVersionSource": "remote",
"requireCommit": true
},
"build": {
"base": {
"corepack": true
},

"development": {
"extends": "base",
"developmentClient": true,
"distribution": "internal",
"env": {
"APP_VARIANT": "development"
},
"channel": "development"
},

"simulator": {
"extends": "development",
"ios": {
"simulator": true
}
},

"preview": {
"extends": "base",
"distribution": "internal",
"channel": "preview"
},

"production": {
"extends": "base",
"autoIncrement": true,
"channel": "production"
}
},
"submit": {
"production": {}
}
}
```