Libraries that are incompatible with Metro ES Module resolution #36551

brentvatne · 2025-05-02T03:36:05Z

brentvatne
May 2, 2025
Maintainer

In React Native 0.79, the Metro team switched the package.json exports field support to enabled by default — this was first available in React Native 0.72. You can opt out of this in your app by specifying unstable_enablePackageExports: false if you run into related issues. Learn more about Metro’s ES Module resolution.

If libraries that you depend on are incompatible with this change, it may be very obvious (you could see errors such as "... attempted to import the Node standard library module ..."), but it may manifest in subtle ways in your app.

In this discussion, please report any libraries that you have found to be incompatible. Use the following template:

Library name: -
Version: -
Error message: -
How to reproduce: -

Workarounds

If you are impacted by this change, you can work around the incompatibilities by disabling package.json:exports in your Metro config, eg:

// metro.config.js
const { getDefaultConfig } = require('expo/metro-config');

/** @type {import('expo/metro-config').MetroConfig} */
const config = getDefaultConfig(__dirname);

config.resolver.unstable_enablePackageExports = false;

module.exports = config;

If the impacted package uses package.json:exports and has a browser version available, you can also tell Metro to use this browser version until the package is fixed for React Native.

// metro.config.js
const { getDefaultConfig } = require('expo/metro-config');

/** @type {import('expo/metro-config').MetroConfig} */
const config = getDefaultConfig(__dirname);

config.resolver.resolveRequest = function packageExportsResolver(context, moduleImport, platform) {
  // Use the browser version of the package for React Native 
  if (moduleImport === '<package>' || moduleImport.startsWith('<package>/')) {
    return context.resolveRequest(
      {
        ...context,
        unstable_conditionNames: ['browser'],
      },
      moduleImport,
      platform,
    );
  }

  // Fall back to normal resolution
  return context.resolveRequest(context, moduleImport, platform);
};

module.exports = config;

brentvatne · 2025-05-02T03:38:28Z

brentvatne
May 2, 2025
Maintainer Author

Library name: @supabase/supabase-js (actually @supabase/realtime-js, but that is included transitively by the former)
Version: Reproduced on 2.49.4 (latest)
Error message:

The package at "node_modules\ws\lib\stream.js" attempted to import the Node standard library module "stream".

How to reproduce: npx expo install @supabase/supabase-js and then import it import { createClient } from '@supabase/supabase-js'

2 replies

byCedric May 3, 2025
Maintainer

Supabase is aware of the issue and has a path forward. See supabase/supabase-js#1400 (comment) for more info.

byCedric May 9, 2025
Maintainer

Supabase released a fix for this issue in @supabase/[email protected]! You can install this exact version and see if this resolves the issue for you.

Note, supabase is working on getting this version stable for release. Once that's done, it will be released as a normal stable release.

brentvatne · 2025-05-02T03:57:11Z

brentvatne
May 2, 2025
Maintainer Author

Library name: kysely
Version: 0.28.2
Error message:

/var/folders/cb/1mtd_ssd4v1bjj3p5q2xs4hr0000gn/T/expo-bundler-0.512785974229343-1746138053339/index.js:148356:37: error: Invalid expression encountered
              var migration = yield import(/* webpackIgnore: true */(0, _classPrivateFieldLooseBase2.default)(this, _props)[_props].path.join((0, _classPrivateFieldLooseBase2.default)(this, _props)[_props].migrationFolder, fileName));
                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Emitted 1 errors. exiting.
Error: /Users/ark/Desktop/Code/expo-kysely-repro/node_modules/react-native/sdks/hermesc/osx-bin/hermesc -emit-binary -out /var/folders/cb/1mtd_ssd4v1bjj3p5q2xs4hr0000gn/T/expo-bundler-0.512785974229343-1746138053339/index.hbc /var/folders/cb/1mtd_ssd4v1bjj3p5q2xs4hr0000gn/T/expo-bundler-0.512785974229343-1746138053339/index.js -O exited with non-zero code: 2

How to reproduce: this minimal example - https://github.com/goknsh/expo-kysely-repro - ref Can't build Kysely on SDK 53 #36544

2 replies

igalklebanov May 2, 2025

Hey 👋

The error is caused by a dynamic import in optional database migrations primitives. We can't use environment-specific APIs, so require is a no-go. We can't ship breaking changes soon as we just recently released v0.28.

@goknsh created kysely-org/kysely#1452. It requires a CJS build.

We want to get rid of CJS (dual package) and ship ESM only (many libraries already started doing that since require(esm) became a thing, and Node.js 18 reached EoL).

We want to keep supporting expo / react-native.

brentvatne May 2, 2025
Maintainer Author

cc @huntie

huntie · 2025-05-02T10:22:51Z

huntie
May 2, 2025

Thanks @brentvatne! Sorry that some developers are experiencing incompatibilities!

Update: This change hit users, we're on it

Unfortunately, the React Native 0.79 "exports" switchover was wider than we expected — specifically, that this feature hadn't been completely active in previous Expo releases by default, which was part of our open source integration strategy.

We're working closely with Expo and package maintainers to resolve issues for most users as soon as possible. This includes the incoming Metro 0.81.5 hotfix.
Package Exports support remains a breaking change that will need to propagate around the ecosystem to align for modern npm package support in React Native. We've basically kicked off this process, more aggressively than planned(!) — and will now continue on the path of aligning packages ASAP.
The user opt out of resolver.unstable_enablePackageExports = false remains.

Previous breaking change comms

Here are more details for library maintainers:

Likely troubleshooting

[Redacted, defer to other package specific comments and our updated troubleshooting guidance.]

0 replies

byCedric · 2025-05-03T10:41:16Z

byCedric May 3, 2025
Maintainer

This is caused by #36594 - should be fixed soon.

byCedric · 2025-05-03T16:47:02Z

byCedric May 3, 2025
Maintainer

Update: this is merged and should be fixed in [email protected].

Full rollout to all of React Native will depend on the Metro patch here: facebook/metro#1498

brentvatne · 2025-05-02T17:15:57Z

brentvatne
May 2, 2025
Maintainer Author

Library name: axios
Version: All
Error message:

The package at "node_modules/axios/dist/node/axios.cjs" attempted to import the Node standard library module "crypto"

How to reproduce: import the axios package. ref: React Native 0.79.1 errors axios/axios#6899

0 replies

petrusvanegeraat · 2025-05-03T06:18:24Z

petrusvanegeraat
May 3, 2025

- Library name: firebase
- Version: 11.6.1 (probably all, only tried the latest version)
- Error message:

Error: Component auth has not been registered yet

- How to reproduce: import firebase and initialize / get auth

const auth = initializeAuth(app, { persistence: getReactNativePersistence(AsyncStorage), });

11 replies

Mert-409 May 26, 2025

sorry for the late reply, i was busy in last few weeks. you should import firebase modules from firebase/auth instead of @firebase/auth. you can try this metro config, it worked for me:

// Learn more https://docs.expo.io/guides/customizing-metro
const { getDefaultConfig } = require("expo/metro-config");
const { withNativeWind } = require("nativewind/metro");

/** @type {import('expo/metro-config').MetroConfig} */
const config = getDefaultConfig(__dirname);

config.resolver.sourceExts.push("cjs");
config.resolver.unstable_enablePackageExports = false;

module.exports = withNativeWind(config, { input: "./global.css" });

marcos-credfranco May 26, 2025

@Mert-409
It didn't work for me.

Expo config

{
  name: 'App Comercial',
  slug: 'app-gerente',
  version: '2.0.2',
  description: undefined,
  sdkVersion: '53.0.0',
  platforms: [
    'ios',
    'android',
    'web'
  ],
  orientation: 'portrait',
  icon: './assets/images/icon.png',
  scheme: 'app-gerente',
  userInterfaceStyle: 'automatic',
  newArchEnabled: true,
  plugins: [
    'expo-router',
    [
      'expo-splash-screen',
      {
        image: './assets/images/cfLogo.png',
        imageWidth: 200,
        resizeMode: 'contain',
        backgroundColor: '#ffffff',
        dark: {
          backgroundColor: '#000000',
          image: './assets/images/cfWhiteLogo.png'
        }
      }
    ],
    'expo-font',
    '@config-plugins/react-native-blob-util',
    '@config-plugins/react-native-pdf',
    'expo-localization',
    'expo-secure-store',
    [
      'expo-camera',
      {
        cameraPermission: 'Allow $(PRODUCT_NAME)  to access your camera',
        microphonePermission: 'Allow $(PRODUCT_NAME) to access your microphone',
        recordAudioAndroid: true
      }
    ],
    [
      'expo-document-picker',
      {
        iCloudContainerEnvironment: 'Production'
      }
    ],
    [
      'expo-image-picker',
      {
        photosPermission: 'O $(PRODUCT_NAME) precisa ter permissão para acessar a galeria.',
        cameraPermission: 'Allow $(PRODUCT_NAME) to access your camera',
        microphonePermission: 'Allow $(PRODUCT_NAME) to access your microphone'
      }
    ],
    [
      'expo-secure-store',
      {
        configureAndroidBackup: true,
        faceIDPermission: 'Permitir que $(PRODUCT_NAME) acesse seus dados biométricos.'
      }
    ],
    '@react-native-firebase/app',
    [
      'expo-build-properties',
      {
        ios: {
          useFrameworks: 'static',
          podfileProperties: {
            'use_modular_headers!': true
          }
        }
      }
    ]
  ],
  _internal: {
    isDebug: false,
    projectRoot: 'D:\\Trabalho\\gerente_app',
    dynamicConfigPath: 'D:\\Trabalho\\gerente_app\\app.config.js',
    packageJsonPath: 'D:\\Trabalho\\gerente_app\\package.json',
    staticConfigPath: {},
    pluginHistory: {
      'expo-splash-screen': {
        name: 'expo-splash-screen',
        version: '0.30.8'
      },
      'expo-font': {
        name: 'expo-font',
        version: '13.3.1'
      },
      'react-native-blob-util': {
        name: 'react-native-blob-util',
        version: '0.22.0'
      },
      'react-native-pdf': {
        name: 'react-native-pdf',
        version: '6.7.7'
      },
      'expo-secure-store': {
        name: 'expo-secure-store',
        version: '14.2.3'
      },
      'expo-camera': {
        name: 'expo-camera',
        version: '16.1.6'
      },
      'expo-document-picker': {
        name: 'expo-document-picker',
        version: '13.1.5'
      },
      'expo-image-picker': {
        name: 'expo-image-picker',
        version: '16.1.4'
      },
      '@react-native-firebase/app': {
        name: '@react-native-firebase/app',
        version: '22.2.0'
      }
    }
  },
  ios: {
    googleServicesFile: './GoogleService-Info.plist',
    usesIcloudStorage: true,
    userInterfaceStyle: 'automatic',
    supportsTablet: true,
    bundleIdentifier: 'com.credfranco.appgerente',
    icon: './assets/images/icon.png',
    infoPlist: {
      ITSAppUsesNonExemptEncryption: false,
      NSFaceIDUsageDescription: 'Face ID é usado para autenticar o usuário.'
    }
  },
  android: {
    googleServicesFile: './google-services.json',
    userInterfaceStyle: 'automatic',
    edgeToEdgeEnabled: true,
    package: 'com.credfranco.appgerente',
    permissions: [
      'android.permission.READ_EXTERNAL_STORAGE',
      'android.permission.WRITE_EXTERNAL_STORAGE',
      'android.permission.DOWNLOAD_WITHOUT_NOTIFICATION',
      'android.permission.ACCESS_NETWORK_STATE',
      'com.google.android.gms.permission.AD_ID',
      'android.permission.CAMERA',
      'android.permission.RECORD_AUDIO'
    ],
    adaptiveIcon: {
      foregroundImage: './assets/images/adaptive-icon.png',
      backgroundColor: '#ffffff'
    }
  },
  web: {
    bundler: 'metro',
    output: 'static',
    favicon: './assets/images/favicon.png'
  },
  experiments: {
    typedRoutes: true
  },
  extra: {
    router: {},
    eas: {
      projectId: ''
    }
  },
  runtimeVersion: {
    policy: 'appVersion'
  },
  updates: {
    url: 'https://u.expo.dev/...'
  },
  androidStatusBar: {
    backgroundColor: '#ffffff'
  }
}

Package.json

{
  "name": "gerente_app",
  "main": "expo-router/entry",
  "version": "1.0.0",
  "scripts": {
    "start": "expo start",
    "reset-project": "node ./scripts/reset-project.js",
    "android": "DARK_MODE=media expo start --android",
    "ios": "DARK_MODE=media expo start --ios",
    "web": "DARK_MODE=media expo start --web",
    "lint": "expo lint",
    "format": "prettier --write .",
    "prebuild": "expo prebuild --clean",
    "android:clean": "expo run:android --no-build-cache"
  },
  "dependencies": {
    "@config-plugins/react-native-blob-util": "^9.0.0",
    "@config-plugins/react-native-pdf": "^9.0.0",
    "@dev-plugins/react-query": "^0.3.1",
    "@expo-google-fonts/inter": "^0.3.0",
    "@expo/html-elements": "^0.12.5",
    "@expo/vector-icons": "^14.1.0",
    "@gluestack-ui/accordion": "^1.0.14",
    "@gluestack-ui/actionsheet": "^0.2.53",
    "@gluestack-ui/alert": "^0.1.16",
    "@gluestack-ui/alert-dialog": "^0.1.38",
    "@gluestack-ui/avatar": "^0.1.18",
    "@gluestack-ui/button": "^1.0.14",
    "@gluestack-ui/checkbox": "^0.1.39",
    "@gluestack-ui/divider": "^0.1.10",
    "@gluestack-ui/fab": "^0.1.28",
    "@gluestack-ui/form-control": "^0.1.19",
    "@gluestack-ui/icon": "^0.1.27",
    "@gluestack-ui/image": "^0.1.17",
    "@gluestack-ui/input": "^0.1.38",
    "@gluestack-ui/link": "^0.1.29",
    "@gluestack-ui/menu": "^0.2.43",
    "@gluestack-ui/modal": "^0.1.41",
    "@gluestack-ui/nativewind-utils": "^1.0.26",
    "@gluestack-ui/overlay": "^0.1.22",
    "@gluestack-ui/popover": "^0.1.49",
    "@gluestack-ui/pressable": "^0.1.23",
    "@gluestack-ui/progress": "^0.1.18",
    "@gluestack-ui/radio": "^0.1.40",
    "@gluestack-ui/select": "^0.1.31",
    "@gluestack-ui/slider": "^0.1.32",
    "@gluestack-ui/spinner": "^0.1.15",
    "@gluestack-ui/switch": "^0.1.29",
    "@gluestack-ui/textarea": "^0.1.25",
    "@gluestack-ui/toast": "^1.0.9",
    "@gluestack-ui/tooltip": "^0.1.44",
    "@hookform/resolvers": "^5.0.1",
    "@legendapp/motion": "^2.4.0",
    "@react-native-async-storage/async-storage": "2.1.2",
    "@react-native-community/datetimepicker": "8.3.0",
    "@react-native-community/netinfo": "11.4.1",
    "@react-native-firebase/analytics": "^22.1.0",
    "@react-native-firebase/app": "^22.1.0",
    "@react-native-segmented-control/segmented-control": "2.5.7",
    "@react-navigation/bottom-tabs": "^7.3.10",
    "@react-navigation/drawer": "^7.3.9",
    "@react-navigation/elements": "^2.3.8",
    "@react-navigation/native": "^7.1.6",
    "@reduxjs/toolkit": "^2.8.1",
    "@shopify/flash-list": "1.7.6",
    "@tanstack/react-query": "^5.75.5",
    "axios": "^1.9.0",
    "babel-plugin-module-resolver": "^5.0.2",
    "chroma-js": "^3.1.2",
    "dayjs": "^1.11.13",
    "expo": "~53.0.9",
    "expo-auth-session": "~6.1.5",
    "expo-blur": "~14.1.4",
    "expo-build-properties": "~0.14.6",
    "expo-camera": "~16.1.6",
    "expo-clipboard": "~7.1.4",
    "expo-constants": "~17.1.6",
    "expo-device": "~7.1.4",
    "expo-document-picker": "~13.1.5",
    "expo-file-system": "~18.1.9",
    "expo-font": "~13.3.0",
    "expo-haptics": "~14.1.4",
    "expo-image": "~2.1.7",
    "expo-image-picker": "~16.1.4",
    "expo-linear-gradient": "~14.1.4",
    "expo-linking": "~7.1.4",
    "expo-local-authentication": "~16.0.4",
    "expo-localization": "~16.1.5",
    "expo-notifications": "~0.31.1",
    "expo-router": "~5.0.7",
    "expo-screen-capture": "~7.1.4",
    "expo-secure-store": "~14.2.3",
    "expo-splash-screen": "~0.30.8",
    "expo-status-bar": "~2.2.3",
    "expo-symbols": "~0.4.4",
    "expo-system-ui": "~5.0.7",
    "expo-task-manager": "~13.1.5",
    "expo-updates": "~0.28.12",
    "expo-web-browser": "~14.1.6",
    "firebase": "^11.8.1",
    "lodash": "^4.17.21",
    "lucide-react-native": "^0.506.0",
    "nativewind": "^4.1.23",
    "react": "19.0.0",
    "react-dom": "19.0.0",
    "react-hook-form": "^7.56.3",
    "react-native": "0.79.2",
    "react-native-blob-util": "^0.22.0",
    "react-native-capture-protection": "^2.0.4",
    "react-native-css-interop": "^0.1.22",
    "react-native-gesture-handler": "~2.24.0",
    "react-native-masked-text": "^1.13.0",
    "react-native-pdf": "^6.7.7",
    "react-native-reanimated": "^3.17.5",
    "react-native-safe-area-context": "^5.4.0",
    "react-native-screens": "~4.10.0",
    "react-native-svg": "15.11.2",
    "react-native-toast-message": "^2.3.0",
    "react-native-ui-datepicker": "^3.1.2",
    "react-native-version-check": "^3.5.0",
    "react-native-version-check-expo": "^3.5.0",
    "react-native-web": "~0.20.0",
    "react-native-webview": "13.13.5",
    "react-redux": "^9.2.0",
    "tailwindcss": "3.4.17",
    "use-count-up": "^3.0.1",
    "yup": "^1.6.1"
  },
  "devDependencies": {
    "@babel/core": "^7.25.2",
    "@tanstack/eslint-plugin-query": "^5.74.7",
    "@types/chroma-js": "^3.1.1",
    "@types/lodash": "^4.17.16",
    "@types/react": "~19.0.10",
    "eslint": "^9.26.0",
    "eslint-config-expo": "~9.2.0",
    "eslint-config-prettier": "^10.1.3",
    "eslint-plugin-prettier": "^5.4.0",
    "jscodeshift": "0.15.2",
    "prettier": "^3.5.3",
    "typescript": "~5.8.3"
  },
  "private": true
}

bilal1031 May 31, 2025

@Mert-409, I am facing a similar issue after making changes in the metro.config.js. The problem is still happening for me.

Error:

Error: Component auth has not been registered yet, js engine: hermes

Metro Config:

// Learn more https://docs.expo.io/guides/customizing-metro
const { getDefaultConfig } = require("expo/metro-config");

/** @type {import('expo/metro-config').MetroConfig} */
const config = getDefaultConfig(__dirname);

config.resolver.sourceExts.push("cjs");
config.resolver.unstable_enablePackageExports = false;

module.exports = config;

Packages Version:

"expo": "53.0.9",
"firebase": "^11.1.0",

Import Statements

import { doc, getFirestore, initializeFirestore } from "firebase/firestore";
import { getApp, getApps, initializeApp } from "firebase/app";
import {
  getAuth,
  initializeAuth,
  onAuthStateChanged,
  // @ts-ignore
  getReactNativePersistence,
} from "firebase/auth";

marcos-credfranco Jun 18, 2025

@bilal1031 try with the "firebase": "11.5.0", here the app loaded, but I'm trying to solve the return to the app expo-auth-session/providers/google, which stopped working

marcos-credfranco Jun 27, 2025

@bilal1031 @Mert-409

Packages Version:

"expo": "53.0.13",
  "firebase": "^11.9.1",

Metro Config:

config.resolver.sourceExts.push('cjs');
config.resolver.unstable_enablePackageExports = false;

tsConfig.json

 "compilerOptions": {
    "strict": true,
    "paths": {
      "@/*": [
        "./*"
      ],
      "@firebase/auth": [
        "./node_modules/@firebase/auth/dist/index.rn.d.ts"
      ]
    }
  },

Import Statements

import {
//@ts-ignore
getReactNativePersistence,
initializeAuth,
} from 'firebase/auth';
import { FirebaseOptions, initializeApp } from 'firebase/app';

Results

The app stopped having the error (Component auth has not been registered yet), however, the redirection after login.

expo-auth-session/providers/google

const [_, response, promptAsync] = Google.useAuthRequest( 
{ 
iosClientId: getConstants('IOS_CLIENT_ID'), 
androidClientId: getConstants('ANDROID_CLIENT_ID'), 
scopes: ['email', 'profile'], 
responseType: Platform.OS === 'web' ? 'id_token' : undefined, 
redirectUri: makeRedirectUri({ 
native: `${getUniqueIdentifier()}://`, 
}), 
// Platform.OS === 'web' 
// ? window.location.origin 
// : `${getUniqueIdentifier()}://`, 
}, 
{ 
native: `${getUniqueIdentifier()}://`, 
} 
);
const { id_token } = response.params; 
const credential = GoogleAuthProvider.credential(id_token); 

signInWithCredential(auth, credential)

kerbe · 2025-05-05T08:31:11Z

kerbe
May 5, 2025

Library name: AWS Amplify
Version: v5
Error message:

[runtime not ready]: TypeError: Cannot read property '__extends' of undefined, js engine: hermes

How to reproduce:
I have been using AWS Amplify for AWS Cognito to do authentication in my app. Import Amplify and create AuthProvider which imports Auth from @aws-amplify/auth.
Workaround:
Adding config.resolver.unstable_enablePackageExports = false; to metro.config.js works, and everything seems to be functioning as before.

Amplify v5 isn't latest, but AWS Amplify itself states that old projects should keep on using v5 while they are still working on migration tools for latest v6.

6 replies

afidhu May 6, 2025

sorry sir help me to fix this bug

The package at "node_modules\ws\lib\stream.js" attempted to import the Node standard library module "stream"
i use supabase, before sdk 52 my app work work after introduce sdk 53 does not run

kerbe May 6, 2025

@kerbe - it'd be great for amplify to backport a fix for that to their v5 release, have you created an issue on their end?

I have not created issue to their repo, at least not yet. I must confess that I don't complete understand this change in Expo/Metro so I would understood what to actually report there, or explaining how they could improve their package regarding this problem. 😬

brentvatne May 7, 2025
Maintainer Author

@afidhu - yes, update your metro.config.js as stated in the OP:

// metro.config.js
const { getDefaultConfig } = require('expo/metro-config');

/** @type {import('expo/metro-config').MetroConfig} */
const config = getDefaultConfig(__dirname);

config.resolver.unstable_enablePackageExports = false;

module.exports = config;

DomGarza May 21, 2025

Library name: AWS Amplify

Version: v5

Error message:
[runtime not ready]: TypeError: Cannot read property '__extends' of undefined, js engine: hermes
How to reproduce:
I have been using AWS Amplify for AWS Cognito to do authentication in my app. Import Amplify and create AuthProvider which imports Auth from @aws-amplify/auth.

Workaround:
Adding config.resolver.unstable_enablePackageExports = false; to metro.config.js works, and everything seems to be functioning as before.

Amplify v5 isn't latest, but AWS Amplify itself states that old projects should keep on using v5 while they are still working on migration tools for latest v6.

Does your Authenticator.Proivder wrapper still work? After getting passes the metro config, my app just crashes with the auth.

Im able to isolate the issue with a basic index.js but it still crashes once I try to do anything with it

kerbe May 21, 2025

Does your Authenticator.Proivder wrapper still work? After getting passes the metro config, my app just crashes with the auth.

I have not used Authenticator.Provider in my codebase, nor never used it (I suppose it is from @aws-amplify/ui-react package, or that at least looks like what you might refer to...).

I have created my own auth flow, and I am creating my own auth provider with React context etc.

@DomGarza you should make minimum repro, so expo team can possibly help when they can see the code & try it out.

Just pay attention that if you use Expo Go to test things out, you use only Amplify Gen 1 way of doing things, and pay attention that you have at maximum v5 packages. If you try to use Gen 2 way, you need to use development builds, not Expo Go. So extra attention on Amplify package versions and style how they are initialized & used is needed.

brentvatne · 2025-05-07T20:53:04Z

brentvatne May 7, 2025
Maintainer Author

@Aksoz @bfar97 @mobinni - are you able to share a minimal reproducible example? also, can you share your babel.config.js and metro.config.js? i suspect you may be using the react-native presets rather than expo presets, which do not have a patch the @byCedric made to fix a bug in metro

anandth · 2025-05-08T06:01:29Z

anandth May 8, 2025

"defaultConfig.resolver.unstable_enablePackageExports = false;" config does not have an effect on metro bundled expo web.

[runtime not ready]: ReferenceError: Property 'require'
doesn't exist, js engine: hermes, stack:
anonymous@1289:24
global@4056:2

anandth · 2025-05-09T03:54:32Z

anandth May 9, 2025

here is my babel.config.js:
module.exports = function(api) {
api.cache(true);
return {
presets: [
['babel-preset-expo', {
// Enable the import.meta transformation for Hermes compatibility
unstable_transformImportMeta: true,
// Enable JSX resolution for require issue
jsxRuntime: 'automatic'
}]
],plugins: [
'react-native-reanimated/plugin',
['module-resolver', {
root: ['./src', '../shared'],
extensions: ['.ios.js', '.android.js', '.js', '.ts', '.tsx', '.json'],
alias: {
'@': './src',
'@snv': '../',
'@shared': '../shared',
'@components': './src/components',
'@screens': './src/screens',
'@hooks': './src/hooks',
'@services': './src/services'
}
}]
]
};
};

metro.config.js

const { getDefaultConfig } = require('expo/metro-config');
const path = require('path');

const projectRoot = __dirname;
const sharedRoot = path.resolve(projectRoot, '../shared');
const workspaceRoot = path.resolve(projectRoot, '../..');

const config = getDefaultConfig(projectRoot);

config.resolver.unstable_enablePackageExports = false;

// Use our custom transformer to inject polyfills
config.transformer.babelTransformerPath = require.resolve('./metro-transformer.js');

// Add shared workspace to watch folders
config.watchFolders = [workspaceRoot, sharedRoot];

// Add shared workspace to resolver
config.resolver.nodeModulesPaths = [
path.resolve(projectRoot, 'node_modules'),
path.resolve(sharedRoot, 'node_modules'),
path.resolve(workspaceRoot, 'node_modules'),
];

// Set up the alias resolver for @shared and other packages
config.resolver.extraNodeModules = {
...config.resolver.extraNodeModules,
'@shared': path.resolve(projectRoot, '../shared'),
'@react-native-async-storage/async-storage': path.resolve(projectRoot, 'node_modules/@react-native-async-storage/async-storage'),
'@react-native-community/netinfo': path.resolve(projectRoot, 'node_modules/@react-native-community/netinfo'),
'expo-notifications': path.resolve(projectRoot, 'node_modules/expo-notifications'),
'expo-location': path.resolve(projectRoot, 'node_modules/expo-location'),
'expo-task-manager': path.resolve(projectRoot, 'node_modules/expo-task-manager'),
'expo-background-fetch': path.resolve(projectRoot, 'node_modules/expo-background-fetch'),
'expo-constants': path.resolve(projectRoot, 'node_modules/expo-constants'),
'expo': path.resolve(projectRoot, 'node_modules/expo'),
'react-native-background-fetch': path.resolve(projectRoot, 'node_modules/react-native-background-fetch'),
'realm': path.resolve(projectRoot, 'node_modules/realm'),
'@realm/react': path.resolve(projectRoot, 'node_modules/realm'),
};

// Comment out custom URL polyfill assignment; use runtime import instead
// const { URL } = require('whatwg-url');
// global.URL = URL;

module.exports = config;

package.json

{
"name": "driver-app",
"version": "1.0.0",
"main": "index.js",
"scripts": {
"start": "expo start",
"android": "expo run:android",
"ios": "expo run:ios",
"web": "expo start --web",
"postinstall": "patch-package"
},
"dependencies": {
"@expo/config-plugins": "~10.0.0",
"@react-native-async-storage/async-storage": "2.1.2",
"@react-native-community/netinfo": "^11.4.1",
"@react-navigation/bottom-tabs": "^7.2.0",
"@react-navigation/native": "^7.1.6",
"@react-navigation/native-stack": "^7.2.0",
"@react-navigation/stack": "^7.2.0",
"@reduxjs/toolkit": "^2.6.1",
"@segment/analytics-react-native": "^2.19.0",
"@segment/sovran-react-native": "^1.1.0",
"@sentry/react-native": "~6.10.0",
"@types/date-fns": "^2.6.3",
"@types/react": "~19.0.10",
"@types/react-native-vector-icons": "^6.4.18",
"axios": "^1.7.9",
"date-fns": "^4.1.0",
"expo": "~53.0.9",
"expo-background-fetch": "~13.1.5",
"expo-constants": "~17.1.6",
"expo-device": "^7.1.4",
"expo-image-picker": "~16.1.4",
"expo-location": "~18.1.4",
"expo-notifications": "~0.31.1",
"expo-secure-store": "^14.2.3",
"expo-status-bar": "~2.2.3",
"expo-task-manager": "~13.1.5",
"lucide-react-native": "^0.503.0",
"react": "19.0.0",
"react-native": "0.79.2",
"react-native-chart-kit": "^6.12.0",
"react-native-gesture-handler": "~2.24.0",
"react-native-get-random-values": "^1.11.0",
"react-native-maps": "1.20.1",
"react-native-paper": "^5.13.1",
"react-native-reanimated": "~3.17.4",
"react-native-safe-area-context": "5.4.0",
"react-native-screens": "~4.10.0",
"react-native-svg": "15.11.2",
"react-native-vector-icons": "^10.2.0",
"react-redux": "^9.2.0",
"realm": "^20.1.0",
"socket.io-client": "^4.8.1",
"whatwg-url": "^14.2.0",
"zustand": "^5.0.3"
},
"devDependencies": {
"@babel/core": "^7.25.2",
"@react-native-community/cli": "latest",
"@types/react-native": "^0.73.0",
"@types/whatwg-url": "^13.0.0",
"babel-plugin-module-resolver": "^5.0.2",
"expo-module-scripts": "^4.0.5",
"metro-react-native-babel-transformer": "^0.77.0",
"patch-package": "^8.0.0",
"postinstall-postinstall": "^2.1.0",
"typescript": "^5.3.3"
},
"private": true,
"expo": {
"doctor": {
"reactNativeDirectoryCheck": {
"exclude": [
"react-native-chart-kit"
],
"listUnknownPackages": false
}
}
}
}

Aksoz · 2025-05-09T07:33:32Z

Aksoz May 9, 2025

Sure, here is a minimal reproducible example:

Versions:

expo: 53.0.*

react-native: 0.79.2

redux-saga: 1.3.0

metro.config.js:

const { getDefaultConfig } = require("expo/metro-config");

const defaultConfig = getDefaultConfig(__dirname);

defaultConfig.resolver.unstable_enablePackageExports` = false;

module.exports = defaultConfig;

babel.config.js

module.exports = function (api) {
  api.cache(true);
  return {
    presets: ["babel-preset-expo"],
  };
};

appStore.js (redux-saga is responsible for undefined default import)

import createSagaMiddleware from "redux-saga";
const sagaMiddleware = createSagaMiddleware();

To be more clear about the issue I am having, I have 0 issues on android and ios, after using defaultConfig.resolver.unstable_enablePackageExports = false;`, but the issue

(0 , _reduxSaga.default) is not a function)

persists on metro bundled web.

HashCookie · 2025-05-11T12:25:38Z

HashCookie May 11, 2025

I have the same problem.

brentvatne · 2025-05-07T20:52:52Z

brentvatne May 7, 2025
Maintainer Author

@dawidzawadzki - are you able to share a minimal reproducible example? i cannot reproduce this. also, can you share your babel.config.js and metro.config.js? i suspect you may be using the react-native presets rather than expo presets, which do not have a patch the @byCedric made to fix a bug in metro

dawidzawadzki · 2025-05-07T21:10:36Z

dawidzawadzki May 7, 2025

Yes, I was using react-native presets. I changed to expo presets and works fine now. Thanks for your help.

marcel-happyfloat · 2025-05-07T19:42:29Z

marcel-happyfloat
May 7, 2025

In case somebody else runs into this issue after upgrading to 53 (even if it's not related to this specific issue, but I wasted hours not knowing where it was coming from):

[runtime not ready]: ReferenceError: Property 'document' doesn't exist, js engine: hermes

styled-components/styled-components#5576

4 replies

EliG-TA May 20, 2025

@marcel-happyfloat Hey! I am getting:

[runtime not ready]: TypeError: initialize is not a function (it is undefined), js engine: hermes
anonymous
    &platform=ios&dev=true&hot=false&transform.engine=hermes&transform.bytecode=1&transform.routerRoot=app&unstable_transformProfile=hermes-stable:35564:14
loadModuleImplementation
    &platform=ios&dev=true&hot=false&transform.engine=hermes&transform.bytecode=1&transform.routerRoot=app&unstable_transformProfile=hermes-stable:253:13
guardedLoadModule
    &platform=ios&dev=true&hot=false&transform.engine=hermes&transform.bytecode=1&transform.routerRoot=app&unstable_transformProfile=hermes-stable:162:37
metroRequire
    &platform=ios&dev=true&hot=false&transform.engine=hermes&transform.bytecode=1&transform.routerRoot=app&unstable_transformProfile=hermes-stable:82:91
anonymous
    &platform=ios&dev=true&hot=false&transform.engine=hermes&transform.bytecode=1&transform.routerRoot=app&unstable_transformProfile=hermes-stable:32267:11
loadModuleImplementation
    &platform=ios&dev=true&hot=false&transform.engine=hermes&transform.bytecode=1&transform.routerRoot=app&unstable_transformProfile=hermes-stable:253:13
guardedLoadModule
    &platform=ios&dev=true&hot=false&transform.engine=hermes&transform.bytecode=1&transform.routerRoot=app&unstable_transformProfile=hermes-stable:155:46
metroRequire
    &platform=ios&dev=true&hot=false&transform.engine=hermes&transform.bytecode=1&transform.routerRoot=app&unstable_transformProfile=hermes-stable:82:91
global
    &platform=ios&dev=true&hot=false&transform.engine=hermes&transform.bytecode=1&transform.routerRoot=app&unstable_transformProfile=hermes-stable:426623:3

philipe-grendene Jun 9, 2025

Any solution?

librod89 Jun 26, 2025

This was fixed for me by upgrading styled-components to v6.1.19

rauldoesnothing Jul 22, 2025

I had the same error. I still don't know what fixed it but I'm glad this metro config change helped me switch to expo v53

wcastand · 2025-05-08T17:36:05Z

wcastand
May 8, 2025

Library name: @tamagui/lucide-icons
Version: 1.126.8 (most likely all)
Error message: Warning

Attempted to import the module "/Volumes/dev/retails/node_modules/victory-native" which is listed in the "exports" of "/Volumes/dev/retails/node_modules/victory-native", however no match was resolved for this request (platform = ios). Falling back to file-based resolution. Consider updating the call site or asking the package maintainer(s) to expose this API.

How to reproduce: import of the icon

import { CircleHelp } from "@tamagui/lucide-icons"

I fixed the issue for now using a babel plugin to force esm export instead, without it tamagui error about config missing :

[
				"transform-imports",
				{
					"@tamagui/lucide-icons": {
						preventFullImport: true,
						skipDefaultConversion: true,
						transform: (importName) => `@tamagui/lucide-icons/dist/esm/icons/${importName}`,
					},
				},
			],

0 replies

wcastand · 2025-05-08T17:37:24Z

wcastand
May 8, 2025

Library name: victory-native
Version: 41.17.1 (most likely all)
Error message: Warning

Attempted to import the module "/Volumes/dev/retails/node_modules/victory-native" which is listed in the "exports" of "/Volumes/dev/retails/node_modules/victory-native", however no match was resolved for this request (platform = ios). Falling back to file-based resolution. Consider updating the call site or asking the package maintainer(s) to expose this API.

How to reproduce: import victory native component

import { Pie, PolarChart } from "victory-native"

0 replies

Failah · 2025-05-14T08:16:47Z

Failah
May 14, 2025

Library name: @react-native-firebase/analytics
Version: "^22.2.0"
Error message: ERROR TypeError: 0, _superstruct.define is not a function (it is undefined), js engine: hermes

How to reproduce:

import _analytics from '@react-native-firebase/analytics'

it started just after updating from expo 52 to expo 53 (never had before). By just removing the import and the related code in the same file, the issue disappears and the app launches correctly.

Any help?

0 replies

DeveloperMCD · 2025-05-16T21:11:31Z

DeveloperMCD
May 16, 2025

I'm having this problem, only in Expo SDK 53. If I run this exact code in the latest SDK 52, it runs perfectly.

ERROR Warning: TypeError: Cannot read property 'getState' of undefined

This error is located at:

80 | }
81 |

82 | export const AuthProvider: React.FC = ({ children }) => {
| ^
83 | const [user, setUser] = useState<User | null>(null);
84 | const [loading, setLoading] = useState(true);
85 | const router = useRouter();

Call Stack
AuthProvider (src/contexts/AuthContext.tsx:82:69)
GluestackUIProvider (src/components/ui/gluestack-ui-provider/index.tsx:26:4)
RNCSafeAreaProvider ()
AppProviders (src/components/App/AppProviders.tsx:22:33)
RootLayout (src/app/_layout.tsx:10:47)
RNCSafeAreaProvider ()
App ()
ErrorOverlay ()

4 replies

Gitarcitano May 19, 2025

The same issue is happening here, every file that uses useState returns the same problem.

DeveloperMCD May 19, 2025

What I don't get, is why this only happens on SDK 53. Because if I used the very latest SDK 52, with this exact same codebase, everything just works. What changed on such a fundamental level?

DeveloperMCD May 19, 2025

Here is the file where the crash is occurring --
AuthContext.tsx.txt

ERROR Warning: TypeError: Cannot read property 'getState' of undefined

This error is located at:

80 | }
81 |

82 | export const AuthProvider: React.FC = ({ children }) => {
| ^
83 | const [user, setUser] = useState<User | null>(null);
84 | const [loading, setLoading] = useState(true);
85 | const router = useRouter();

Call Stack
AuthProvider (src/contexts/AuthContext.tsx:82:69)
GluestackUIProvider (src/components/ui/gluestack-ui-provider/index.tsx:26:4)

Gitarcitano May 29, 2025

@DeveloperMCD Maybe this fix will help to address this issue:
#37023

But this fix is not released yet

akhil-gautam · 2025-05-27T08:12:31Z

akhil-gautam
May 27, 2025

iOS Bundling failed 25101ms node_modules/expo-router/entry.js (3163 modules)
The package at "node_modules/@expo/config-plugins/build/utils/XML.js" attempted to import the Node standard library module "fs".
It failed because the native React runtime does not include the Node standard library.

My package.json:

{
  "name": "expo-app",
  "main": "expo-router/entry",
  "version": "1.0.0",
  "scripts": {
    "start": "expo start --tunnel",
    "start-web": "expo start --web --tunnel",
    "start-web-dev": "DEBUG=expo* expo start --web --tunnel"
  },
  "dependencies": {
    "@expo/vector-icons": "^14.1.0",
    "@react-native-async-storage/async-storage": "2.1.2",
    "@react-native-community/datetimepicker": "8.3.0",
    "@react-native-picker/picker": "^2.11.0",
    "@react-navigation/native": "^7.1.9",
    "expo": "^53.0.9",
    "expo-blur": "~14.1.4",
    "expo-calendar": "~14.1.4",
    "expo-constants": "~17.1.6",
    "expo-font": "~13.3.1",
    "expo-haptics": "~14.1.4",
    "expo-health-connect": "^0.1.1",
    "expo-image": "~2.1.7",
    "expo-image-picker": "~16.1.4",
    "expo-linear-gradient": "~14.1.4",
    "expo-linking": "~7.1.5",
    "expo-location": "~18.1.5",
    "expo-router": "~5.0.7",
    "expo-splash-screen": "~0.30.8",
    "expo-status-bar": "~2.2.3",
    "expo-symbols": "~0.4.4",
    "expo-system-ui": "~5.0.7",
    "expo-web-browser": "~14.1.6",
    "lucide-react-native": "^0.475.0",
    "nativewind": "^4.1.23",
    "react": "19.0.0",
    "react-dom": "19.0.0",
    "react-native": "0.79.1",
    "react-native-gesture-handler": "~2.24.0",
    "react-native-health": "^1.19.0",
    "react-native-reanimated": "~3.17.5",
    "react-native-safe-area-context": "5.3.0",
    "react-native-screens": "~4.10.0",
    "react-native-svg": "15.11.2",
    "react-native-web": "^0.20.0",
    "zustand": "^5.0.5"
  },
  "devDependencies": {
    "@babel/core": "^7.27.1",
    "@expo/ngrok": "^4.1.3",
    "@types/react": "~19.0.14",
    "typescript": "~5.8.3"
  },
  "private": true
}

1 reply

akhil-gautam May 27, 2025

The package at "node_modules/@expo/config-plugins/build/plugins/withAndroidBaseMods.js" attempted to import the Node standard library module "fs".
It failed because the native React runtime does not include the Node standard library.

finnyfound · 2025-05-30T14:36:24Z

finnyfound
May 30, 2025

Library name: redux-saga
Version: 1.3.0 (latest)
Error message:

runtime not ready TypeError _reduxSaga.default is not a function(it is undefined)

How to reproduce:

import createSagaMiddleware from 'redux-saga';
const sagaMiddleware = createSagaMiddleware();

0 replies

fendyk · 2025-05-31T21:25:53Z

fendyk
May 31, 2025

Library name: Tanstack-form
Version: >= 1.11.0

Error message: See link

How to reproduce:
see issue: https://github.com/TanStack/form/issues/1534

0 replies

byCedric · 2025-06-10T11:01:35Z

byCedric
Jun 10, 2025
Maintainer

Library name: @sinclair/typebox
Version: 0.34.33

Error message:

Metro error: Cannot read properties of undefined (reading 'defineProperty')

How to reproduce: See #37171
Related issue: See sinclairzx81/typebox#1256

0 replies

dantecorrea1 · 2025-06-13T02:08:13Z

dantecorrea1
Jun 13, 2025

Thank you!!!

0 replies

KoenCa · 2025-06-19T15:37:35Z

KoenCa
Jun 19, 2025

Library name: React Hook Form Zod schema resolver
Version: Zod version 4 with @hookform/resolvers version 5.1.0 or higher.
Error message: none, see issue: [React Native] Zod v4 locale and global error customization not picked up react-hook-form/resolvers#785
How to reproduce: see issue: [React Native] Zod v4 locale and global error customization not picked up react-hook-form/resolvers#785

0 replies

meatnordrink · 2025-06-24T12:50:27Z

meatnordrink
Jun 24, 2025

Is there any possibility this would affect TS resolution? I noticed that the Jest matchers added by expo-router are, since the 53 upgrade, throwing type errors. They function fine, but TS seems to be missing the new types added by expo-router now.

Library name: - expo-router
Version: - 5.1.0
Error message: - TS error
How to reproduce: - Upgrade to 53, note TS error on any toHavePathname etc. assertions, added by expo-router.

2 replies

meatnordrink Jun 24, 2025

It seems like this was the case - at least according to Claude 4.2. 🤷

Root Cause: The issue was caused by SDK 53's new package.json exports field being enabled by default in Metro bundler, which changed how TypeScript resolves type definitions. The toHavePathname, toHaveSearchParams, and other Jest matchers from expo-router/testing-library were working at runtime but TypeScript couldn't find their type definitions.

Workaround - jest-expo-router.d.ts:

/// <reference types="expo-router/types/expect" />

jerone Jun 24, 2025

See #33851

Reykjavik151 · 2025-06-25T11:50:33Z

Reykjavik151
Jun 25, 2025

Some issue with Firebase initialisation.
Trying to get expoPushToken on Android real device - no chance.

"expo": "53.0.11",
"expo-notifications": "0.31.3"

Seems connected to the Forebase initialisation after Expo SDK 53 upgrade. Any help?

1 reply

jlo1 Jul 1, 2025

for firebase, i needed to set enablePackageExports to false, and also add cjs to my sourceExts

#36588 (comment)

AndreyPassos · 2025-06-26T00:20:59Z

AndreyPassos
Jun 26, 2025

I tried several previous configurations, but I still got the error "Service firestore is not available". So far I have tested some versions of firebase along with expo sdk 52 and 53.

0 replies

shaibusunnuma · 2025-07-16T01:44:21Z

shaibusunnuma
Jul 16, 2025

Library name: @usewaypoint/email-builder
Version: 0.0.8
Error message:

Attempted to import the module "/AppPath/node_modules/react-dom/server.browser.js" which is not listed in the "exports" of "/AppPath/node_modules/react-dom" under the requested subpath "./server.browser.js". Falling back to file-based resolution. Consider updating the call site or asking the package maintainer(s) to expose this API.

How to Reproduce*: Create a dom component that imports and uses a functionality from @usewaypoint/email-builder with exp sdk 53

0 replies

mgray88 · 2025-07-21T15:38:26Z

mgray88
Jul 21, 2025

Does anyone else use firebase-admin for their expo-router server-side api routes? This issue only occurs when upgrading from SDK 52 to SDK 53. firebase-admin works fine in api routes under SDK 52.

Library name: firebase-admin
Version: 13.4.0
Error message:

λ Bundled 1578ms src/app/api/user/index+api.ts (1226 modules)

Metro error: Cannot read properties of undefined (reading 'Auth')

   9 | import log from "@/utils/logger";
  10 | import { eq, getTableColumns } from "drizzle-orm";
> 11 | import { FirebaseAuthError } from "firebase-admin/auth";
     | ^
  12 | import type { Simplify } from "type-fest";
  13 | import { ApiError, type Middleware } from "../api-handler";
  14 | import { firebaseAuth } from "../firebase";

How to reproduce: Import firebase-admin in any expo-router api route

0 replies

wmaca-friday · 2025-07-21T15:59:50Z

wmaca-friday
Jul 21, 2025

In my case, I had a custom babel.config.js that used @react-native/babel-preset instead of babel-preset-expo. Replacing it solved the problem reported at #36635.

0 replies

rauldoesnothing · 2025-07-22T22:37:26Z

rauldoesnothing
Jul 22, 2025

In React Native 0.79, the Metro team switched the package.json exports field support to enabled by default — this was first available in React Native 0.72. You can opt out of this in your app by specifying unstable_enablePackageExports: false if you run into related issues. Learn more about Metro’s ES Module resolution.

If libraries that you depend on are incompatible with this change, it may be very obvious (you could see errors such as "... attempted to import the Node standard library module ..."), but it may manifest in subtle ways in your app.

In this discussion, please report any libraries that you have found to be incompatible. Use the following template:

Library name: -

Version: -

Error message: -

How to reproduce: -

Workarounds

If you are impacted by this change, you can work around the incompatibilities by disabling package.json:exports in your Metro config, eg:
// metro.config.js
const { getDefaultConfig } = require('expo/metro-config');

/** @type {import('expo/metro-config').MetroConfig} */
const config = getDefaultConfig(__dirname);

config.resolver.unstable_enablePackageExports = false;

module.exports = config;
If the impacted package uses package.json:exports and has a browser version available, you can also tell Metro to use this browser version until the package is fixed for React Native.
// metro.config.js
const { getDefaultConfig } = require('expo/metro-config');

/** @type {import('expo/metro-config').MetroConfig} */
const config = getDefaultConfig(__dirname);

config.resolver.resolveRequest = function packageExportsResolver(context, moduleImport, platform) {
  // Use the browser version of the package for React Native 
  if (moduleImport === '<package>' || moduleImport.startsWith('<package>/')) {
    return context.resolveRequest(
      {
        ...context,
        unstable_conditionNames: ['browser'],
      },
      moduleImport,
      platform,
    );
  }

  // Fall back to normal resolution
  return context.resolveRequest(context, moduleImport, platform);
};

module.exports = config;

This fixed my migration from expo v52 to v53. I have 0 clue what packages weren't compatible but I'm so hyped it works again

0 replies

Libraries that are incompatible with Metro ES Module resolution #36551

Uh oh!

Uh oh!

brentvatne May 2, 2025 Maintainer

Workarounds

Replies: 27 comments · 44 replies

Uh oh!

brentvatne May 2, 2025 Maintainer Author

Uh oh!

byCedric May 3, 2025 Maintainer

Uh oh!

byCedric May 9, 2025 Maintainer

Uh oh!

brentvatne May 2, 2025 Maintainer Author

Uh oh!

Uh oh!

Uh oh!

brentvatne May 2, 2025 Maintainer Author

Uh oh!

Uh oh!

Update: This change hit users, we're on it

Previous breaking change comms

Likely troubleshooting

This comment has been hidden.

Uh oh!

byCedric May 3, 2025 Maintainer

Uh oh!

byCedric May 3, 2025 Maintainer

Uh oh!

Uh oh!

brentvatne May 2, 2025 Maintainer Author

Uh oh!

Uh oh!

Uh oh!

Expo config

Package.json

Uh oh!

Uh oh!

Error:

Metro Config:

Packages Version:

Import Statements

Uh oh!

Uh oh!

Packages Version:

Metro Config:

tsConfig.json

Import Statements

Results

Uh oh!

Uh oh!

Uh oh!

Uh oh!

brentvatne May 7, 2025 Maintainer Author

Uh oh!

Uh oh!

Uh oh!

This comment was marked as off-topic.

Uh oh!

Uh oh!

brentvatne May 7, 2025 Maintainer Author

Uh oh!

brentvatne
May 2, 2025
Maintainer

Replies: 27 comments 44 replies

brentvatne
May 2, 2025
Maintainer Author

byCedric May 3, 2025
Maintainer

byCedric May 9, 2025
Maintainer

brentvatne
May 2, 2025
Maintainer Author

brentvatne May 2, 2025
Maintainer Author

byCedric May 3, 2025
Maintainer

byCedric May 3, 2025
Maintainer

brentvatne
May 2, 2025
Maintainer Author

brentvatne May 7, 2025
Maintainer Author

brentvatne May 7, 2025
Maintainer Author