[Bug]: Code fails to bundle with API routes

[Nezz]

Which Platforms?

Both

Which React Native Version?

0.81.5

Which @braze/react-native-sdk SDK version?

18.0.0

Repro Rate

100%

Steps To Reproduce

The code bunding fails when a project has Expo API Routes.

Minimal repro project: https://github.com/Nezz/expo-repro/tree/repro/Braze

Steps:

1. Run bun install
2. Run bun expo export:embed --eager --platform ios --dev false

Expected Behavior

The code bunding should work

Actual Incorrect Behavior

Bundling the code fails:

Error: Importing native-only module "react-native/Libraries/Utilities/codegenNativeComponent" on web from: node_modules/@braze/react-native-sdk/src/specs/BrazeBannerViewNativeComponent.ts

Import stack:

 node_modules/@braze/react-native-sdk/src/specs/BrazeBannerViewNativeComponent.ts
 | import "react-native/Libraries/Utilities/codegenNativeComponent"
           ^ Importing react-native internals is not supported on web.

 node_modules/@braze/react-native-sdk/src/ui/braze-banner-view.js
 | import "../specs/BrazeBannerViewNativeComponent"

 node_modules/@braze/react-native-sdk/src/braze.js
 | import "./ui/braze-banner-view"

 node_modules/@braze/react-native-sdk/src/index.js
 | import "./braze"

 app/(tabs)/index.tsx
 | import "@braze/react-native-sdk"

Verbose Logs

Additional Information

It'd be nice to provide a polyfill for web for this to work out of the box

[jerielng]

Hey @Nezz! Thanks for reporting this. We'll take a deeper look into the minimal reproducible project you provided and keep you updated. If we could confirm a couple of things to understand this case a little better:

• In your report, you mentioned this is happening on both platforms - just wanted to confirm this, similarly to the command you provided, this should also occur on bun expo export:embed --eager --platform android --dev false as well?
• I noticed in the error trace that the message mentions web even though the compilation command was to build iOS, which is likely because Expo API Routes is a web-first library. If this is the case, this would more likely be part of a feature request to support web as a platform. Currently, our Expo plugin is designed for mobile platforms only.

[Nezz]

this should also occur on bun expo export:embed --eager --platform android --dev false as well?

Yes. Not sure why the web routes get bundled when building for mobile, but that's what Expo does.

I noticed in the error trace that the message mentions web even though the compilation command was to build iOS, which is likely because Expo API Routes is a web-first library.

Yes, it basically targets web in order to run the API routes in a Node.js environment. A noop shim would work, I ended up overriding the Braze SDK with just this on the web:

const Braze = {
  changeUser: (_userId) => {},
  setEmail: (_email) => {},
  setFirstName: (_firstName) => {},
  setLastName: (_lastName) => {},
};

export default Braze;

Although it gets more complicated with all the possible SDK methods.

[jerielng]

That makes sense. Thanks for the clarification! A no-op shim like you mentioned could be a possibility here. Our team will have to investigate our options deeper as a feature request - we've filed an internal ticket to do so. Thanks for raising this to our attention, and we will keep you updated here with anything!