From 525cb6117b79498e0241de02a13b30621efbc28f Mon Sep 17 00:00:00 2001 From: Rob Hogan Date: Mon, 3 Mar 2025 04:09:14 -0800 Subject: [PATCH] metro-config: Don't always assert import/require with unstable_enablePackageExports (#49780) Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/49780 Now that we're using a minimum Metro version of 0.81.3, Metro will dynamically assert `import` or `require` based on the style of the import at source. Asserting both is likely to cause issues with `babel/runtime` and potentially other packages - see https://github.com/facebook/metro/pull/1447. Changelog: [Internal] metro-config: Assert import/require dynamically when using `unstable_enablePackageExports` with Metro. Reviewed By: hoxyq Differential Revision: D70473577 --- packages/metro-config/src/index.flow.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/metro-config/src/index.flow.js b/packages/metro-config/src/index.flow.js index 1c68e400739..0a3b7c39969 100644 --- a/packages/metro-config/src/index.flow.js +++ b/packages/metro-config/src/index.flow.js @@ -53,7 +53,7 @@ export function getDefaultConfig(projectRoot: string): ConfigT { resolver: { resolverMainFields: ['react-native', 'browser', 'main'], platforms: ['android', 'ios'], - unstable_conditionNames: ['require', 'import', 'react-native'], + unstable_conditionNames: ['react-native'], }, serializer: { // Note: This option is overridden in cli-plugin-metro (getOverrideConfig)