Can't use with unstable_enablePackageExports metro option (expo)

[aldebout]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

When using @supabase/supabase-js in an expo react native project, if I use the unstable_enablePackageExports with the metro bundler, bundling fails with the following error:

To Reproduce

1. Generate a new expo app
2. Add @supabase/supabase-js as a dependency
3. Create a supabase client in the main _layout.tsx file
4. Run npx expo customize metro.config.js
5. Add config.resolver.unstable_enablePackageExports = true; to metro.config.js
6. Add ios.bundleIdentifier to app.json
7. Run npx expo run:ios

Repro repo: https://github.com/aldebout/supabase-expo-exports-issue

Expected behavior

No crash

Screenshots

System information

• OS: macOS
• Version of supabase-js: 2.45.1
• Version of Node.js: 20.16.0

Additional information

Opening here because the error message I got in my actual project was

The package at "../../node_modules/@supabase/realtime-js/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.

[practiv-wamci]

Is there any update on this? I've run into the same issue

[filipecabaco]

now that we have native ws support I do think that we can remove ws which seems to be the source of the issue.

#426 here's a branch for us to use for testing to see if we can fix it by removing ws from realtime-js dependencies.

but after removing it I keep getting the same issue and the only dependency that uses it's node_modules/@expo/cli 😞 . what could be the way to fix it?

[aldebout]

@filipecabaco I'm not sure what the next step is, how can I help you?

[filipecabaco]

@aldebout maybe. it seems that the main issue was the fact that we had the ws dependency which created issues with expo. the PR #426 removes said dependency.

could you try to checkout the repo, checkout the branch fix/remove-ws-lib and override the dependency to check if it's not something related to my environment?

[aldebout]

I tried using the branch but I'm having issues because package.json references the build outputs (/dist/...) and they're not in the github source code :/
When you tested locally, did you use npm with overrides or a local link? I've had issues with npm overrides in the past, it might work better with yarn or pnpm.

[filipecabaco]

I need to try it again but if I'm not mistaken I did use overrides... maybe I should just make an example with just realtime-js and expo to make it easier to test out without overrides and just importing the "fix branch"

[DanielVolchek]

Any update? Currently running into this issue as well

@filipecabaco

[filipecabaco]

sorry not yet as we were tackling other issues on the server side. I also need to do another fix in realtime-js and then I will pick this one up again

as mentioned above I'm going to create a new repo with realtime-js so we can test this in a more consistent way to find a fix 👀

[DanielVolchek]

@filipecabaco

OK, no problem. I can confirm that by using patch package to imitate your pr like so it solved the issue for me

[filipecabaco]

FYI I've merged #444 so 2.11.4-next.1 will have this code.

I do need some help testing this change, if possible do override realtime-js in supabase-js with this version

[filipecabaco]

Did a new change to have it as an optionalDependency and also to have a script to remove modules if Expo is present
#448

[byCedric]

Unfortunately, this is still an issue due to the inlining of import('ws') here. Starting from Expo SDK 53 - package.json:exports are now enabled by default, making @supabase/supabase-js and @supabase/realtime-js unusable with the default settings.

Related: expo/expo#36375