expo / expo/eas-cli

Local builds always use bun 1.3, but shouldn't.

Open
#3,238 1 comment 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

_No response_

### Summary

Since around a week we can't build our Expo 53 project locally (e.g. Android), as the `eas build --local` command always uses bun 1.3.1 in our bun workspace to install dependencies. As soon as we build in the cloud, everything works as expected because the image used uses bun 1.2.x.

We couldn't find a way to force the local build to use bun 1.2.x.

Is it intended, that the local command always uses the latest bun release? I guess no all packages are yet compatible with bun 1.3.

### Managed or bare?

Bare

### Environment

expo-env-info 2.0.7 environment info:
System:
OS: macOS 15.6.1
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.19.0 - /usr/local/bin/node
Yarn: 1.22.22 - ~/.yarn/bin/yarn
npm: 10.2.3 - /usr/local/bin/npm
Watchman: 2025.06.23.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.16.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 24.2, iOS 18.2, macOS 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2
IDEs:
Android Studio: 2025.1 AI-251.26094.121.2513.14007798
Xcode: 16.2/16C5032a - /usr/bin/xcodebuild
npmGlobalPackages:
eas-cli: 16.24.1
Expo Workflow: bare

### Error output

_No response_

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

Can't

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.