Skip to content

Update glob paths for internal and common modules #8854

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
Bernier154 wants to merge 1 commit into from
Closed

Update glob paths for internal and common modules #8854

Bernier154 wants to merge 1 commit into from
+4 −4

Conversation

@Bernier154
Copy link

@Bernier154 Bernier154 commented Jan 23, 2026 •
edited
Loading

Description

Fixing the exports problem:

 WARN  The package [projectURL]/node_modules/@react-native-firebase/app contains an invalid package.json configuration. Consider raising this issue with the package maintainer(s).
Reason: The resolution for "[projectURL]/node_modules/@react-native-firebase/app/lib/internal/nativeModule" defined in "exports" is [projectURL]/node_modules/@react-native-firebase/app/dist/module/internal/nativeModule, however this file does not exist. Falling back to file-based resolution.
 WARN  The package [projectURL]/node_modules/@react-native-firebase/app contains an invalid package.json configuration. Consider raising this issue with the package maintainer(s).
Reason: The resolution for "[projectURL]/node_modules/@react-native-firebase/app/lib/internal/NativeFirebaseError" defined in "exports" is [projectURL]/node_modules/@react-native-firebase/app/dist/module/internal/NativeFirebaseError, however this file does not exist. Falling back to file-based resolution.
 WARN  The package [projectURL]/node_modules/@react-native-firebase/app contains an invalid package.json configuration. Consider raising this issue with the package maintainer(s).
Reason: The resolution for "[projectURL]/node_modules/@react-native-firebase/app/lib/common/deeps" defined in "exports" is [projectURL]/node_modules/@react-native-firebase/app/dist/module/common/deeps, however this file does not exist. Falling back to file-based resolution.
 WARN  The package [projectURL]/node_modules/@react-native-firebase/app contains an invalid package.json configuration. Consider raising this issue with the package maintainer(s).
Reason: The resolution for "[projectURL]/node_modules/@react-native-firebase/app/lib/common/validate" defined in "exports" is [projectURL]/node_modules/@react-native-firebase/app/dist/module/common/validate, however this file does not exist. Falling back to file-based resolution.
 WARN  The package [projectURL]/node_modules/@react-native-firebase/app contains an invalid package.json configuration. Consider raising this issue with the package maintainer(s).
Reason: The resolution for "[projectURL]/node_modules/@react-native-firebase/app/lib/internal/SharedEventEmitter" defined in "exports" is [projectURL]/node_modules/@react-native-firebase/app/dist/module/internal/SharedEventEmitter, however this file does not exist. Falling back to file-based resolution.

Related issues

Release Summary

Edition of the two glob path for the common and internal folder.

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

Did not test i edited the two entries package.json in my personal project directly.

But after a made the modification I rebuilt both android and apple and all react native firebase functions works now.

I my simulator i even have AppCheck + expo54 working without problem (problem mentionned here)
#8829 (comment)

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

@vercel
Copy link

vercel bot commented Jan 23, 2026

@Bernier154 is attempting to deploy a commit to the Invertase Team on Vercel.

A member of the Team first needs to authorize it.

@CLAassistant
Copy link

CLAassistant commented Jan 23, 2026

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@Bernier154 Bernier154 closed this Jan 23, 2026
@Bernier154
Copy link
Author

Bernier154 commented Jan 23, 2026 •
edited
Loading

In favor of #8848

@Bernier154 Bernier154 deleted the fix-exports-package-json branch January 23, 2026 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

Needs Attention

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[🐛] v23.8.0 .1 and .2 have a publishing regression - Expo plugin config is not valid - remain on 23.7.0 or wait for 23.8.3+

2 participants

@Bernier154 @CLAassistant