Bundling for Web attempts to import node.js modules from dependencies due to improper compiler environment selection

Do you want to request a feature or report a bug?

Report a Bug

What is the current behavior?

When importing libraries like 'firebase' who depend use 'browser' as the main target and compiling for a metro 'browser' / web target the compiler still attempts to load node.js dependencies when it should not.

This has been previously reported to firebase-js-sdk but their staff believe this is a metro compiler issue.

See https://github.com/firebase/firebase-js-sdk/issues/7849#issuecomment-1857889012

If the current behavior is a bug, please provide the steps to reproduce and a minimal repository on GitHub that we can yarn install and yarn test.

I will attempt to build you a repository for testing this as soon as I can.

This is easily reproduce when importing firebase@10.11 and attempting to access the firebase/auth package.

What is the expected behavior?

Only browser dependencies should load in a browser-based build.

Please provide your exact Metro configuration and mention your Metro, node, yarn/npm version and operating system.

Start by reproducing the issue with firebase@10.11, the firebase/auth package, and a Metro browser/web target. Investigate the compiler environment selection and verify that the browser build no longer attempts to load Node.js dependencies; the issue does not name specific files or tests.