Skip to content

Conversation

@mikehardy
Copy link
Collaborator

@mikehardy mikehardy commented Jan 16, 2026

Description

The packages migrated to typescript have explicit exports statements in package.json which restrict what entry points may be accessed when standard node module resolution rules are followed

Expo config plugins uses a resolver that follows those rules, so it was following the exports declarations that are new in the typescript-migrated packages

Ergo, if we are going to specify exports, we must also specify the expo plugin export, or it can't be resolved via module resolution rules used by expo and the plugin fails to load

Related issues

Not marking it as a "fix" yet because there is still an outstanding issue for other/web reported by a user, but this should fix expo users on android / ios

Release Summary

fix release commit, should generate a fix release

Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
    • Yes
  • My change supports the following platforms;
    • Android
    • iOS
    • Other (macOS, web)
  • My change includes tests;
    • e2e tests added or updated in packages/\*\*/e2e
    • jest tests added or updated in packages/\*\*/__tests__
  • I have updated TypeScript types that are affected by my change.
  • This is a breaking change;
    • Yes
    • No

Test Plan

I have an almost-completely-working expo build demo of react-native-firebase working now:

https://github.com/mikehardy/rnfbdemo/blob/rnfb-expo-demo/make-expo-demo.sh

Most importantly for this PR, when I got it working to the point where it configured the config plugins, I reproduced the error (as hoped!) that was reported in #8829

I was able to track it down to the exports fields in the package.json of the migrated packages and verify expo prebuild worked correctly via directly manipulating the package.json files in node_modules there, then carried that fix here to this PR


Think react-native-firebase is great? Please consider supporting the project with any of the below:

if we are going to specify exports, we must also specify the plugin
export, or it is not resolveable via module resolution rules used
by expo and the plugin fails to load
@vercel
Copy link

vercel bot commented Jan 16, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
react-native-firebase Ready Ready Preview, Comment Jan 16, 2026 4:14am

Review with Vercel Agent

@mikehardy mikehardy merged commit 7ae0872 into main Jan 16, 2026
24 of 25 checks passed
@mikehardy mikehardy deleted the @mikehardy/expo-plugins-fix branch January 16, 2026 10:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants