Consider Adding react-native to the exports Field in package.json

[sukminkang12]

Why?

Zustand is widely used across multiple frameworks. As a React Native developer, I've been impressed by the convenience that Zustand offers.

In React Native's default bundler, Metro, the default value for the unstable_enablePackageExports option was recently set to true. Since React Native now specifies unstable_conditionNames: ['react-native'], the bundler looks at the exports field of Zustand during the build process, leading to ESM-based bundling.

However, Hermes, the JavaScript engine used by React Native, doesn't support ESM, resulting in errors.

My Suggestion

In the package.json, could we add a react-native condition to the exports field and have it use CommonJS (CJS) instead of ESM? This change would help avoid the errors caused by ESM incompatibility with Hermes.

With the growing number of developers using Zustand for state management in React Native, I believe this adjustment would be beneficial to many.

[dai-shi]

See also: pmndrs/jotai#3041 (comment)

I'm waiting for feedback.

[sukminkang12]

@dai-shi Thanks!

[dai-shi]

Would you like to help evaluating it? I think we should check how it works for various RN versions and configs.

[sukminkang12]

@dai-shi
I've shared my thoughts in the link you provided.