Unable to use in React Native due to import.meta not being supported

[malord]

React Native's Hermes JavaScript engine doesn't support import.meta and exits with an error at compile time, so testing for its existence in code doesn't work. I'm tempted to file a bug for this against Hermes but wondered whether any way around this already existed for Zustand?

[dai-shi]

If import.meta isn't supported, it means ESM isn't supported, I guess.
So, RN's Hermes should use CJS instead of ESM. (But, I don't think it's ideal.)

Our intentional workaround is to use "module" condition instead of "import" condition, but I'm afraid Hermes doesn't support those conditions in the first place. 🤔

@barelyhuman Do we have similar issues reported? We use the same config across zustand/jotai/valtio, and I suspect there are RN users who use Hermes...

[dai-shi]

Could Zustand add react-native export as described in the proposal?

I'm fine to add "react-native" condition that points to CJS. Not sure if it's an ultimate solution.

[zgid123]

I am not sure, but it seems if I use config.resolver.unstable_conditionNames = ['require'];, expo-router file-based router won't work

[dai-shi]

That's interesting. I expected if conditionNames are ['require'] it will fallback to "default".

https://nodejs.org/docs/latest/api/packages.html#conditional-exports

---

Can you try config.resolver.unstable_conditionNames = ['require', 'default'];?

[zgid123]

still raise error [Error: URL.pathname not implemented]

[zgid123]

this config can make zustand to work for expo when enablePackageExports is enabled

config.resolver.unstable_conditionNames = [
  'browser',
  'require',
  'react-native',
]