Rob Hogan fe2bcbf4ba Community CLI: Don't clobber user config of Metro resolver/serializer, expose CLI config to user as defaults (#51836) ...

Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/51836

Currently, `community-cli-plugin` loads the user config and then overrides parts of it - specifically `resolver.resolveRequest` and `serializer.getModulesRunBeforeMainModule`, making it impossible for a user to modify this config.

Instead, treat the CLI's resolver and serializer customisations as "Framework defaults", layered on top of `react-native/metro-config` defaults but beneath a user's `metro.config.js`.

This allows the user to obtain (via `react-native/metro-config`'s `getDefaultConfig`) and extend or override them, if they need to.

This is technically breaking because users who currently have a custom `resolveRequest` or `getModulesRunBeforeMainModule` in their `metro.config.js` will have that config respected from this change, whereas currently they won't have any effect.

Changelog:
[General][Breaking] Community CLI users: user-defined `resolver.resolveRequest` and `serializer.getModulesRunBeforeMainModule` Metro config now takes precedence over CLI defaults

Reviewed By: huntie

Differential Revision: D74811395

fbshipit-source-id: c250caf798fdaedb0822bea3d6e65c0c3ae4d691

2025-06-09 07:44:02 -07:00

..

commands

RN: Flowify packages/rn-tester (#51788)

2025-06-04 12:03:52 -07:00

utils

Community CLI: Don't clobber user config of Metro resolver/serializer, expose CLI config to user as defaults (#51836)

2025-06-09 07:44:02 -07:00

index.flow.js

RN: Delete @oncall Annotations (#51416)

2025-05-17 16:18:05 -07:00

index.js

RN: Delete @oncall Annotations (#51416)

2025-05-17 16:18:05 -07:00