search

expo / eas-cli

Fastest way to build, submit, and update iOS and Android apps
https://docs.expo.dev/eas/
MIT License
706 stars 76 forks source link

[EAS Build] EAS Build should adhere to the package manager version set in package.json #2401

Open pmk1c opened 1 month ago

pmk1c commented 1 month ago

I was confused at first, when I noticed that EAS ignores the packageManager field in package.json. I think this should be the first place to look for, when EAS decides, which package manager and which version to use.

szdziedzic commented 2 weeks ago

Hi @pmk1c,

It makes sense. I will try to add support for it and make it the first place to look for package manager + its version đź‘Ť

expo-bot commented 2 weeks ago

Thank you for filing this issue! This comment acknowledges we believe this may be a bug and there’s enough information to investigate it. However, we can’t promise any sort of timeline for resolution. We prioritize issues based on severity, breadth of impact, and alignment with our roadmap. If you’d like to help move it more quickly, you can continue to investigate it more deeply and/or you can open a pull request that fixes the cause.

expo-bot commented 2 weeks ago

Thank you for filing this issue! This comment acknowledges we believe this may be a bug and there’s enough information to investigate it. However, we can’t promise any sort of timeline for resolution. We prioritize issues based on severity, breadth of impact, and alignment with our roadmap. If you’d like to help move it more quickly, you can continue to investigate it more deeply and/or you can open a pull request that fixes the cause.

FedeRBeije commented 6 hours ago

Hello, i'm using turborepo monorepo and trying to build some apps.

If in my root there is a packageManager prop like this: image

that is automatically added by turborepo, i'd get this error in eas log:

We detected that 'APP_NAME' is a yarn workspace Running "yarn install" in /Users/expo/workingdir/build directory error This project's package.json defines "packageManager": "yarn@npm@10.8.1". However the current global version of Yarn is 1.22.21. Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19. Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack. yarn install exited with non-zero code: 1

Do you have any suggestion of why is happening?

Also i'm using npm as package manager.

Thank you