-
Notifications
You must be signed in to change notification settings - Fork 872
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.
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
Add a Node ESM build to RUT #6360
Conversation
🦋 Changeset detectedLatest commit: 3968d08 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Size Report 1Affected ProductsNo changes between base commit (8f82660) and merge commit (183e367).Test Logs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Size Analysis Report 1Affected ProductsNo changes between base commit (8f82660) and merge commit (455c433).Test Logs |
Thanks a lot for the fix! |
So my proposed diagnostic/solution was right? Thanks for the credit 😉 |
Rules-unit-testing only had a CJS build for Node. This causes it to load the CJS build of Firestore, while the user may load methods from an Node ESM build of Firestore, if their project uses ES modules. This causes there to be two copies of Firestore instances that don't match.
Tested on repro: https://github.com/MarkDuckworth/firebase-js-sdk-issues-6080 and it fixes the issue.
Fixes #6080