T3-Turbo Installing Expo Packages Error

Hey, when I try to add packages or update packages to my expo app in create-t3-turbo it tries running random npm commands...
yarn add v1.22.19
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
warning @shopify/flash-list > recyclerlistview > prop-types > fbjs > [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
[6/6] ⠄ @acme/db
[-/6] ⠄ waiting...
[-/6] ⠄ waiting...
[-/6] ⠄ waiting...
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
error C:\......\node_modules\@acme\db: Command failed.
Exit code: 1
Command: prisma generate
Arguments:
yarn add v1.22.19
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
warning @shopify/flash-list > recyclerlistview > prop-types > fbjs > [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
[6/6] ⠄ @acme/db
[-/6] ⠄ waiting...
[-/6] ⠄ waiting...
[-/6] ⠄ waiting...
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
error C:\......\node_modules\@acme\db: Command failed.
Exit code: 1
Command: prisma generate
Arguments:
5 Replies
WOLFLEADER
WOLFLEADEROP2y ago
if I add --npm it works until i want to try add a library with and @
npx expo install @config-plugins/react-native-ble-plx --npm
npx expo install @config-plugins/react-native-ble-plx --npm
chip
chip2y ago
when dealing with expo install, I just cd into the actual expo app dir, and run the cmd there
WOLFLEADER
WOLFLEADEROP2y ago
yea i am running it in apps/expo and i am getting these weird bugs its almost like npm is doing it in root?
chip
chip2y ago
what if you just run npm install <package> --workspace=<workspace>? Or do you NEED to run expo install? I am using turborepo, and doing the same as you, odd I use pnpm tho
WOLFLEADER
WOLFLEADEROP2y ago
yea ive switched to pnpm and its working fine weird i think expo was trying to use yarn which was causing conflicts
Want results from more Discord servers?
Add your server