(Supabase.js not working with expo sdk 53 ? ) The package at "node_modules\ws\lib\stream.js" attempted to import the Node standard library module "stream".

[goxr3plus]

Supabase not working with expo sdk 53 ?

I updated from latest expo sdk 52.0.46 to new expo sdk 53.0.1 , i am also using node 23.11.0 , and i am using eas build . System windows 11.0.0

Everything worked perfectly on expo sdk 52.0.46 with custom dev client and now getting this error

============ error ==========

Android Bundling failed 23470ms index.js (2841 modules)
The package at "node_modules\ws\lib\stream.js" attempted to import the Node standard library module "stream".
It failed because the native React runtime does not include the Node standard library.
Learn more: https://docs.expo.dev/workflow/using-libraries/#using-third-party-libraries

below is my package json with the scripts :

{
  "private": true,
  "name":NoMoneyNoHoney",
  "version": "1.0.0",
  "scripts": {
    "eas-android-development-client-apk": "eas build -p android --profile development",
    "eas-android-development-client-apk-local": "eas build --profile development --platform android --local",
    "android": "expo run:android",
    "ios": "expo run:ios",
    "publish": "expo publish",
    "expo-doctor": "npx expo-doctor@latest",
    "-": "-",
    "deploy": "eas build --platform android",
    "check-updates": "npx npm-check-updates",
    "upgrade-dependencies": "npx expo install --fix",
    "--": "--",
    "eas-android-production-apk": "eas build -p android --profile production-apk",
    "eas-android-local-prod-apk": "eas build --profile production-apk --platform android --local",
    "---": "---",
    "npx_prebuild": "npx expo prebuild --clean",
    "start": "npx expo start --dev-client",
    "clearCache": "npx expo start -c"
  },
  "dependencies": {
    "@expo/metro-config": "~0.20.0",
    "@expo/metro-runtime": "~5.0.4",
    "@expo/prebuild-config": "~9.0.0",
    "@expo/vector-icons": "^14.1.0",
    "@notifee/react-native": "9.1.8",
    "@react-native-async-storage/async-storage": "2.1.2",
    "@react-native-community/netinfo": "11.4.1",
    "@sentry/react-native": "~6.10.0",
    "@shopify/react-native-skia": "v2.0.0-next.2",
    "@supabase/supabase-js": "2.49.4",
    "@types/react": "~19.0.10",
    "axios": "1.9.0",
    "expo": "~53.0.1",
    "expo-application": "~6.1.3",
    "expo-asset": "~11.1.3",
    "expo-auth-session": "~6.1.4",
    "expo-av": "~15.1.3",
    "expo-build-properties": "~0.14.5",
    "expo-clipboard": "~7.1.3",
    "expo-constants": "~17.1.3",
    "expo-crypto": "~14.1.3",
    "expo-dev-client": "~5.1.5",
    "expo-device": "~7.1.3",
    "expo-document-picker": "~13.1.4",
    "expo-file-system": "~18.1.7",
    "expo-image-picker": "~16.1.3",
    "expo-linear-gradient": "~14.1.3",
    "expo-linking": "~7.1.3",
    "expo-sharing": "~13.1.4",
    "expo-splash-screen": "~0.30.6",
    "expo-system-ui": "~5.0.5",
    "expo-web-browser": "~14.1.5",
    "firebase": "11.6.1",
    "lottie-react-native": "7.2.2",
    "qs": "6.14.0",
    "react": "19.0.0",
    "react-dom": "19.0.0",
    "react-native": "0.79.1",
    "react-native-animatable": "1.4.0",
    "react-native-crypto-js": "^1.0.0",
    "react-native-gesture-handler": "~2.24.0",
    "react-native-google-mobile-ads": "14.11.0",
    "react-native-reanimated": "~3.17.4",
    "react-native-redash": "^18.1.3",
    "react-native-safe-area-context": "5.3.0",
    "react-native-screens": "~4.10.0",
    "react-native-svg": "15.11.2",
    "react-native-url-polyfill": "^2.0.0",
    "react-native-view-shot": "~4.0.3",
    "react-native-web": "^0.20.0",
    "react-native-webview": "13.13.5",
    "typescript": "~5.8.3",
    "zustand": "^5.0.3"
  },
  "devDependencies": {
    "@babel/core": "^7.20.0",
    "babel-plugin-module-resolver": "^5.0.2",
    "prettier": "^3.5.3"
  },
  "expo": {
    "doctor": {
      "reactNativeDirectoryCheck": {
        "listUnknownPackages": false
      }
    }
  }
}

So i have builded succesfully a dev-client-apk and i pressed start project and i am getting this weird error and i searched everywhere and i don't know if it's supabase or expo having this issue right now :

It happens just when the app is building and ready to start ..
============ error ==========

Android Bundling failed 23470ms index.js (2841 modules)
The package at "node_modules\ws\lib\stream.js" attempted to import the Node standard library module "stream".
It failed because the native React runtime does not include the Node standard library.
Learn more: https://docs.expo.dev/workflow/using-libraries/#using-third-party-libraries

============================

I did the below to check who is the guilty and maybe it's supabase ?

 npm ls ws

+-- @supabase/supabase-js@2.49.4
| `-- @supabase/realtime-js@2.11.2
|   `-- ws@8.18.1
+-- expo@53.0.1
| `-- @expo/cli@0.24.7
|   +-- @react-native/dev-middleware@0.79.1
|   | `-- ws@6.2.3
|   `-- ws@8.18.1 deduped
`-- react-native@0.79.1
  +-- @react-native/community-cli-plugin@0.79.1
  | `-- metro@0.82.2
  |   `-- ws@7.5.10
  +-- react-devtools-core@6.1.1
  | `-- ws@7.5.10
  `-- ws@6.2.3

I searched for a workaround and tried with polyfill but nothing works .... :

[brentvatne]

hi there! this is the same issue as #1726

the teams at expo and supabase have been discussing this and a fix is in progress. you can disable the package exports configuration in metro as described here:

// 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;

[gokkuu100]

Hi there, is there any solution for this? I am getting the same error and haven't got a fix by now

[goxr3plus]

hi there! this is the same issue as supabase/supabase-js#1726

the teams at expo and supabase have been discussing this and a fix is in progress. you can disable the package exports configuration in metro as described here:

// 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;

it doesn't work :( still same error even after rebuilding eas local development build and cleaning the cache etc etc :

Android Bundling failed 23646ms index.js (2836 modules)
The package at "node_modules\ws\lib\stream.js" attempted to import the Node standard library module "stream".
It failed because the native React runtime does not include the Node standard library.
Learn more: https://docs.expo.dev/workflow/using-libraries/#using-third-party-libraries

@brentvatne

I am going back to expo sdk 52.0.46 :( sad sad :(

My metro config

const { getDefaultConfig } = require('expo/metro-config')
const { getSentryExpoConfig } = require('@sentry/react-native/metro')

const config = getDefaultConfig(__dirname)

// Apply your existing modifications to the defaultConfig
config.transformer.minifierConfig.compress.drop_console = true

// https://stackoverflow.com/questions/72158122/expo-firebase-authentication-while-trying-to-resolve-module-idb-from-file
// Fix for Firebase Authentication module resolution issue
config.resolver.assetExts.push('cjs')

// Add the unstable_conditionNames configuration
config.resolver.unstable_enablePackageExports = false

// Wrap the modified config with Sentry's config
module.exports = getSentryExpoConfig(__dirname, config)

[alisondavidperez]

when are you planning to fix this? should I change Supabase to Firebase as I'm starting a new project?

[marwenrebah]

Are their any updates?

[grdsdev]

Hey everyone, we’re working on a fix for this, thanks for your patience!

[osmanozts]

hi there! this is the same issue as supabase/supabase-js#1726

the teams at expo and supabase have been discussing this and a fix is in progress. you can disable the package exports configuration in metro as described here:

// 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;

This workaround works for thanks 💯. Does this disable supabase realtime or has any consequences ?

[goxr3plus]

hi there! this is the same issue as supabase/supabase-js#1726

the teams at expo and supabase have been discussing this and a fix is in progress. you can disable the package exports configuration in metro as described here:

// 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;

This workaround works for thanks 💯. Does this disable supabase realtime or has any consequences ?

I tried it 4 times and still getting the same error did you rebuild the dev client? I literally tried every solution recommended and getting that error. Can you please tell me what steps did you follow.

[vuzzer]

Hey everyone, we’re working on a fix for this, thanks for your patience!

I'm glad to hear there's progress. It's been two days now that I've been waiting for the bug to be resolved. The project I'm working on is already well advanced and heavily relies on Supabase, which is deeply integrated into the architecture. While migrating to another service is technically possible, it would require a significant time investment—something that’s unfortunately not feasible given the tight delivery deadlines.

[Hultner]

hi there! this is the same issue as supabase/supabase-js#1726

the teams at expo and supabase have been discussing this and a fix is in progress. you can disable the package exports configuration in metro as described here:

// 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;
Thanks!

Adding the false flag to my config works for now:

config.resolver.unstable_enablePackageExports = false;

[safaaa2]

Android Bundling failed 52417ms node_modules\expo-router\entry.js (1501 modules)
The package at "node_modules\ws\lib\stream.js" attempted to import the Node standard library module "stream".
It failed because the native React runtime does not include the Node standard library.
Learn more: https://docs.expo.dev/workflow/using-libraries/#using-third-party-libraries

guys i got this error why ?? please do you know how to fix it ?

[osmanozts]

as @brentvatne mentioned, after adding his suggestion to the metro.config.js i was able to build eas builds for ios and android and was able to run it again on ios. (didnt test android run yet)

[safaaa2]

as @brentvatne mentioned, after adding his suggestion to the metro.config.js i was able to build eas builds for ios and android and was able to run it again on ios. (didnt test android run yet)

please can you help me do you have a contact please??