prisma / react-native-prisma

Apache License 2.0
200 stars 9 forks source link

Support Expo SDK 52 #45

Open dwightwatson opened 1 week ago

dwightwatson commented 1 week ago

I'm not entirely certain what is going on here, but noting it here in case it's not just me. SDK 52 was released today, and after upgrading from 51 to 52 my app will no longer build on EAS.

env: load .env
env: export LOGGING_ENABLED
Starting Metro Bundler
iOS Bundling failed 7961ms node_modules/expo-router/entry.js (1446 modules)
Unable to resolve module .prisma/client/react-native from /Users/expo/workingdir/build/node_modules/@prisma/client/react-native.js: .prisma/client/react-native could not be found within the project or in these directories:
  node_modules
  1 | module.exports = {
> 2 |   ...require('.prisma/client/react-native'),
    |               ^
  3 | }
  4 |
Error: Unable to resolve module .prisma/client/react-native from /Users/expo/workingdir/build/node_modules/@prisma/client/react-native.js: .prisma/client/react-native could not be found within the project or in these directories:
  node_modules
  1 | module.exports = {
> 2 |   ...require('.prisma/client/react-native'),
    |               ^
  3 | }
  4 |
Error: Unable to resolve module .prisma/client/react-native from /Users/expo/workingdir/build/node_modules/@prisma/client/react-native.js: .prisma/client/react-native could not be found within the project or in these directories:
  node_modules
  1 | module.exports = {
> 2 |   ...require('.prisma/client/react-native'),
    |               ^
  3 | }
  4 |
    at ModuleResolver.resolveDependency (/Users/expo/workingdir/build/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:148:15)
    at DependencyGraph.resolveDependency (/Users/expo/workingdir/build/node_modules/metro/src/node-haste/DependencyGraph.js:235:43)
    at /Users/expo/workingdir/build/node_modules/metro/src/lib/transformHelpers.js:160:21
    at resolveDependencies (/Users/expo/workingdir/build/node_modules/metro/src/DeltaBundler/buildSubgraph.js:42:25)
    at visit (/Users/expo/workingdir/build/node_modules/metro/src/DeltaBundler/buildSubgraph.js:83:30)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Promise.all (index 2)
    at visit (/Users/expo/workingdir/build/node_modules/metro/src/DeltaBundler/buildSubgraph.js:92:5)
    at async Promise.all (index 6)
    at visit (/Users/expo/workingdir/build/node_modules/metro/src/DeltaBundler/buildSubgraph.js:92:5)
npx expo export:embed --eager --platform ios --dev false exited with non-zero code: 1

I wonder if it is a change related to bundling in SDK 52, or perhaps some hook/event isn't firing when it previously did.

sergiofra98 commented 1 day ago

I'm not entirely certain what is going on here, but noting it here in case it's not just me. SDK 52 was released today, and after upgrading from 51 to 52 my app will no longer build on EAS.

i have this issue too, the curious thing is that it only occurs during compile time, in expo go it works normally.

my target is SDK 34 and the minimum is 24.

I'm running open JDK and JRE 17, Android SDK with plaform and build-tools 35 and NDK 26.

Both local and cloud builds fail.