Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: use correct node and pnpm versions in eas.json #1285

Merged
merged 1 commit into from
Jan 25, 2025

Conversation

nickreynolds
Copy link
Contributor

The expo app's eas.json file specify node and pnpm versions that are incompatible with the engines specified in the root package.json file.

This is causing EAS builds to fail with the following error:

Running "pnpm install --no-frozen-lockfile" in /home/expo/workingdir/build directory

ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

Your pnpm version is incompatible with "/home/expo/workingdir/build".

Expected version: ^9.14.2

Got: 9.7.0

This is happening because the package's manifest has an engines.pnpm field specified.

To fix this issue, install the required pnpm version globally.

To install the latest version of pnpm, run "pnpm i -g pnpm".

To check your pnpm version, run "pnpm -v".

Your Node version is incompatible with "/home/expo/workingdir/build".

Expected version: >=20.18.1

This PR just updates the versions used in eas.json to match what is required by the monorepo itself.

@juliusmarminge juliusmarminge merged commit 9998e00 into t3-oss:main Jan 25, 2025
3 of 5 checks passed
datagutt pushed a commit to datagutt/create-dat-app that referenced this pull request Feb 20, 2025
VaniaPopovic pushed a commit to VaniaPopovic/create-t3-turbo that referenced this pull request Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants