expo / expo/eas-cli

Check that packages match versions required by installed Expo SDK

Open
#3,133 0 comments 0 reactions 0 assignees View on GitHub
needs review
Dominant language
TypeScript
Stars
1.4k
Forks
236
Avg merge
3d 1h
Merged PRs (30d)
91

Description

### Build/Submit details page URL

https://expo.dev/accounts/qtea/projects/VelvetLadle/builds/754de4a0-7e66-47e7-9965-d3e867d27e7a

### Summary

I have been trying to build a preview/development app. I run the Expo doctor in VS code no issues. I go to build and the build fails. Every single time. It come back with an typescript error.

### Managed or bare?

Bare

### Environment

expo-env-info 1.3.4 environment info:
System:
OS: Windows 11 10.0.26100
Binaries:
Node: 20.10.0 - C:\Program Files\nodejs\node.EXE
npm: 10.2.3 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: AI-243.26053.27.2432.13536105
npmPackages:
expo: ~53.0.20 => 53.0.20
expo-router: ~5.1.4 => 5.1.4
expo-updates: ~0.28.17 => 0.28.17
react: 19.0.0 => 19.0.0
react-dom: 19.0.0 => 19.0.0
react-native: 0.79.5 => 0.79.5
react-native-web: ~0.20.0 => 0.20.0
Expo Workflow: managed

env: load .env.local
env: export EXPO_PUBLIC_SCRAPINGBEE_KEY EXPO_PUBLIC_SPOONACULAR_KEY EXPO_PUBLIC_SUPABASE_URL EXPO_PUBLIC_SUPABASE_ANON_KEY
15/15 checks passed. No issues detected!

### Error output

Running "expo doctor"

Running 15 checks on your project...

14/15 checks passed. 1 checks failed. Possible issues detected:

Use the --verbose flag to see more details about passed checks.

✖ Check that packages match versions required by installed Expo SDK

CommandError: "typescript" is added as a dependency in your project's package.json but it doesn't seem to be installed. Run "npm install", or the equivalent for your package manager, and try again.

Advice:

Use 'npx expo install --check' to review and upgrade your dependencies.

1 check failed, indicating possible issues with the project.

Command "expo doctor" failed.
npx -y expo-doctor exited with non-zero code: 1

Starting Metro Bundler

Android node_modules/expo-router/entry.js ▓▓▓▓▓▓░░░░░░░░░░ 41.7% (330/511)

Android node_modules/expo-router/entry.js ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░ 97.1% (1081/1097)

Android Bundling failed 6570ms node_modules/expo-router/entry.js (1106 modules)

Error: Unable to resolve module @/components/buttons from /home/expo/workingdir/build/app/(auth)/welcome.tsx: @/components/buttons could not be found within the project or in these directories:

node_modules

> 1 | import Button from '@/components/buttons';

| ^

2 | import ImageViewer from '@/components/imageViewer';

3 | import { useAuth } from '@/contexts/AuthContext';

4 | import { useColors } from '@/contexts/ThemeContext';

Error: Unable to resolve module @/components/buttons from /home/expo/workingdir/build/app/(auth)/welcome.tsx: @/components/buttons could not be found within the project or in these directories:

node_modules

> 1 | import Button from '@/components/buttons';

| ^

2 | import ImageViewer from '@/components/imageViewer';

3 | import { useAuth } from '@/contexts/AuthContext';

4 | import { useColors } from '@/contexts/ThemeContext';

at ModuleResolver.resolveDependency (/home/expo/workingdir/build/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:150:15)

at DependencyGraph.resolveDependency (/home/expo/workingdir/build/node_modules/metro/src/node-haste/DependencyGraph.js:239:43)

at /home/expo/workingdir/build/node_modules/metro/src/lib/transformHelpers.js:161:21

at resolveDependencies (/home/expo/workingdir/build/node_modules/metro/src/DeltaBundler/buildSubgraph.js:43:25)

at visit (/home/expo/workingdir/build/node_modules/metro/src/DeltaBundler/buildSubgraph.js:81:30)

at processTicksAndRejections (node:internal/process/task_queues:95:5)

at async Promise.all (index 1)

at visit (/home/expo/workingdir/build/node_modules/metro/src/DeltaBundler/buildSubgraph.js:90:5)

at async Promise.all (index 0)

at visit (/home/expo/workingdir/build/node_modules/metro/src/DeltaBundler/buildSubgraph.js:90:5)

npx expo export:embed --eager --platform android --dev false exited with non-zero code: 1

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

npm run build: preview

> velvetladle@1.0.0 build:preview
> npx eas build --profile preview --platform android

The field "cli.appVersionSource" is not set, but it will be required in the future. Learn more: https://docs.expo.dev/build-reference/app-versions/
Resolved "preview" environment for the build. Learn more: https://docs.expo.dev/eas/environment-variables/#setting-the-environment-for-your-builds
No environment variables with visibility "Plain text" and "Sensitive" found for the "preview" environment on EAS.
Environment variables loaded from the "preview" build profile "env" configuration: NODE_ENV.

You set NODE_ENV=production in the build profile or environment variables. Remember that it will be available during the entire build process. In particular, it will make yarn/npm install only production packages.

The field "cli.appVersionSource" is not set, but it will be required in the future. Learn more: https://docs.expo.dev/build-reference/app-versions/
✔ Using remote Android credentials (Expo server)
✔ Using Keystore from configuration: Build Credentials XUsK3AiFpK (default)

Compressing project files and uploading to EAS Build. Learn more: https://expo.fyi/eas-build-archive
✔ Compressed project files 10s (81.9 MB)
✔ Uploaded to EAS 3m 20s
✔ Computed project fingerprint

See logs: https://expo.dev/accounts/qtea/projects/VelvetLadle/builds/754de4a0-7e66-47e7-9965-d3e867d27e7a

Waiting for build to complete. You can press Ctrl+C to exit.
✖ Build failed

🤖 Android build failed:
Unknown error. See logs of the Bundle JavaScript build phase for more information.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.