@unifold/connect-react-native 0.1.28 → 0.1.30

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +1 -1
  2. package/dist/index.js +2 -2
  3. package/dist/index.mjs +2 -2
  4. package/package.json +2 -2
package/README.md CHANGED
@@ -36,7 +36,7 @@ Link Pay uses `@stripe/stripe-react-native`, which includes **native** code (App
36
36
 
37
37
  Importing `@unifold/connect-react-native` loads the Stripe UI registration in the same JS bundle as the provider. Ensure the peer dependencies in **Installation** above are installed so Metro does not duplicate native modules.
38
38
 
39
- **`expo-constants`** is a **dependency** of `@unifold/connect-react-native` so `require("expo-constants")` always resolves when reading `merchantIdentifier` from the Stripe Expo plugin in JS. You can still set **`config.stripeMerchantIdentifier`** on `UnifoldProvider` to override or skip that path.
39
+ **`expo-constants`** is a **dependency** of `@unifold/connect-react-native`. The prebuilt bundle uses a **static** `import` from `expo-constants` (in the Stripe helper that reads the Expo plugin) so Metro always links the module. (A runtime `require("expo-constants")` in that path was still emitted inside the bundle and could trigger “unknown module” in Metro.) You can still set **`config.stripeMerchantIdentifier`** on `UnifoldProvider` to override or skip reading the plugin from constants.
40
40
 
41
41
  #### Expo Go vs development build vs prebuild
42
42