Restore 'import' in default Package Exports conditions (#36902)

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

Reverts https://github.com/facebook/react-native/pull/36584.

Since we've come across example packages (typically targeting Node.js) which only distribute ESM, we believe it's more helpful to return to asserting the `"import"` condition by default, for maximum compatibility. The above issue and comments outline the pros/cons.

Changelog:
[General][Changed] - Default condition set for experimental Package Exports is now ['require', 'import', 'react-native']

Metro changelog: [Experimental] Package Exports unstable_conditionNames now defaults to ['require', 'import']

Reviewed By: robhogan

Differential Revision: D44962143

fbshipit-source-id: 004172388916c902469b49cfc920ebe13c62c430
This commit is contained in:
Alex Hunt authored and Facebook GitHub Bot committed 2023-04-14 03:39:46 -07:00
1 parent 3b4037e379
commit 808b3c9716
1 file changed
+1 -1
+1 -1
View File
@@ -42,7 +42,7 @@ function getDefaultConfig(
resolver: {
resolverMainFields: ['react-native', 'browser', 'main'],
platforms: ['android', 'ios'],
unstable_conditionNames: ['require', 'react-native'],
unstable_conditionNames: ['require', 'import', 'react-native'],
},
serializer: {
getPolyfills: () => require('@react-native/js-polyfills')(),