`npx create-expo-app@latest` is failing with link-react-compiler-runtime.sh: not found
envgap__expo__expo-31912
01 / FAILURE SIGNATURE
Captured in a clean container
Error: npm install exited with non-zero code: 127
02 / ENVIRONMENT RECIPE
- Base commit
90b13ad9d0dd3469556ac776d8b74643375b1d97- Manifest
templates/expo-template-default/package.json- Reproduce
cd /work/templates/expo-template-default && npm install --workspaces=false --before=2024-10-08T02:00:28Z && npx --no-install expo export --platform web- Run under trace
cd /work/templates/expo-template-default && npx --no-install expo export --platform web
03 / ORIGINAL ISSUE TEXT
expo/expo #31912 · read the original issue
**Edit(@byCedric): if you still run into this issue, check [Expo's comment](https://github.com/expo/expo/issues/31912#issuecomment-2399492631) for more information**
---
### Summary
Suddenly (2024-10-07), if I run `npx create-expo-app@latest TestExpo` the install process gets forever and finally fails with:
### Using npm
```
pm error code 127
npm error path /home/ernesto/Scratchpad/TestExpo/node_modules/babel-plugin-react-compiler
npm error command failed
npm error command sh -c ./scripts/link-react-compiler-runtime.sh
npm error sh: 1: ./scripts/link-react-compiler-runtime.sh: not found
npm error A complete log of this run can be found in: /home/ernesto/.npm/_logs/2024-10-08T01_05_52_912Z-debug-0.log
Something went wrong installing JavaScript dependencies. Check your npm logs. Continuing to create the app.
Error: npm install exited with non-zero code: 127
```
Full logs:
[2024-10-08T01_05_52_912Z-debug-0.log](https://github.com/user-attachments/files/17286221/2024-10-08T01_05_52_912Z-debug-0.log)
### Using yarn
```
[4/4] Building fresh packages...
verbose 32.140710131 Error: /home/ernesto/Scratchpad/TestExpo/node_modules/babel-plugin-react-compiler: Command failed.
Exit code: 127
Command: ./scripts/link-react-compiler-runtime.sh
Arguments:
Directory: /home/ernesto/Scratchpad/TestExpo/node_modules/babel-plugin-react-compiler
Output:
/bin/sh: 1: ./scripts/link-react-compiler-runtime.sh: not found
at ProcessTermError.ExtendableBuiltin (/home/ernesto/.local/share/mise/installs/node/20.17.0/lib/node_modules/yarn/lib/cli.js:721:66)
at ProcessTermError.MessageError (/home/ernesto/.local/share/mise/installs/node/20.17.0/lib/node_modules/yarn/lib/cli.js:750:123)
at new ProcessTermError (/home/ernesto/.local/share/mise/installs/node/20.17.0/lib/node_modules/yarn/lib/cli.js:790:113)
at ChildProcess.<anonymous> (/home/ernesto/.local/share/mise/installs/node/20.17.0/lib/node_modules/yarn/lib/cli.js:25789:17)
at ChildProcess.emit (node:events:519:28)
at maybeClose (node:internal/child_process:1105:16)
at Socket.<anonymous> (node:internal/child_process:457:11)
at Socket.emit (node:events:519:28)
at Pipe.<anonymous> (node:net:339:12)
error /home/ernesto/Scratchpad/TestExpo/node_modules/babel-plugin-react-compiler: Command failed.
Exit code: 127
Command: ./scripts/link-react-compiler-runtime.sh
Arguments:
Directory: /home/ernesto/Scratchpad/TestExpo/node_modules/babel-plugin-react-compiler
Output:
/bin/sh: 1: ./scripts/link-react-compiler-runtime.sh: not found
```
- OS Ubuntu24.04
- Linux 6.8.0-45-generic
- node v20.17.0 installed via [mise](https://mise.jdx.dev/)
- npm v10.9.0
Yesterday I was able to create a project just fine
### What platform(s) does this occur on?
_No response_
### SDK Version
latest
### Environment
```text
expo-env-info 1.2.0 environment info:
System:
OS: Linux 6.8 Ubuntu 24.04.1 LTS 24.04.1 LTS (04 / LABELS
Labels checked by running the task · assistant reviewed
No supported category has been assigned.
Label rules and the text that matched
[]
Historical install-only results are not EnvGap validation.
Full-only already_works control. No failing runtime task is claimed: original install and actual app web export succeed, also under Sciunit tracing.
npm --before selects compiler 0.0.0-experimental-fe484b5-20240912 today. Issue logs identify 0.0.0-experimental-7779988-20241007 as the broken historical latest tag. Timestamp filtering cannot reconstruct npm historical dist-tags; no tag or manifest is altered to force that old failure.
The evaluated original application is templates/expo-template-default; unrelated Expo root/native monorepo packages are not installed. D1/D2 are scoped to this manifest/application.
Expo writes a generated favicon PNG under templates/expo-template-default/.expo/web/cache/production/images. Source enforcement must recognize this narrow generated image-cache path; every tracked source file remains unchanged.
Export validates real Metro bundling and six static route renders, not native Android/iOS builds or browser interaction.
Preparation uses current registries. Historical package availability is not enforced here; execution metadata records this limitation separately from the oracle's date-bounding policy.