plugin-expo-eas-sourcemaps is not compatible with monorepos

[thorbenprimke]

Describe the bug

Add the plugin-expo-eas-sourcemaps config plugin to an expo project in a monorepo. It does not work due to the node_modules path not being what is expected in the scripts.

Steps to reproduce

1. Set up a monorepo with workspaces
2. Add the app at like packages/app
3. Kick off an EAS build and see it fail

Environment

• Bugsnag version: 45.0.0
• Expo SDK version: SDK 45

Example code snippet - patch packages that resolves it (but not in a dynamic manner)

diff --git a/node_modules/@bugsnag/plugin-expo-eas-sourcemaps/lib/bugsnag-expo-xcode.sh b/node_modules/@bugsnag/plugin-expo-eas-sourcemaps/lib/bugsnag-expo-xcode.sh
index cc52c28..bce3d79 100755
--- a/node_modules/@bugsnag/plugin-expo-eas-sourcemaps/lib/bugsnag-expo-xcode.sh
+++ b/node_modules/@bugsnag/plugin-expo-eas-sourcemaps/lib/bugsnag-expo-xcode.sh
@@ -58,4 +58,4 @@ if [ ! -z "$ENDPOINT" ]; then
   ARGS+=("$ENDPOINT")
 fi
 
-../node_modules/.bin/bugsnag-source-maps upload-react-native "${ARGS[@]}"
+../../../node_modules/.bin/bugsnag-source-maps upload-react-native "${ARGS[@]}"
diff --git a/node_modules/@bugsnag/plugin-expo-eas-sourcemaps/src/ios.js b/node_modules/@bugsnag/plugin-expo-eas-sourcemaps/src/ios.js
index e18e9c8..b01bd40 100644
--- a/node_modules/@bugsnag/plugin-expo-eas-sourcemaps/src/ios.js
+++ b/node_modules/@bugsnag/plugin-expo-eas-sourcemaps/src/ios.js
@@ -31,7 +31,7 @@ function withIosPlugin (config, onPremConfig) {
     bundleReactNativePhase.shellScript = modifiedScript
 
     // 03. Configure the new build phase
-    const shellScript = 'SOURCE_MAP="$TMPDIR/$(md5 -qs "$CONFIGURATION_BUILD_DIR")-main.jsbundle.map" ../node_modules/@bugsnag/plugin-expo-eas-sourcemaps/lib/bugsnag-expo-xcode.sh'
+    const shellScript = 'SOURCE_MAP="$TMPDIR/$(md5 -qs "$CONFIGURATION_BUILD_DIR")-main.jsbundle.map" ../../../node_modules/@bugsnag/plugin-expo-eas-sourcemaps/lib/bugsnag-expo-xcode.sh'
 
     xcodeProject.addBuildPhase([], buildPhaseName, 'Upload source maps to Bugsnag', null, {
       shellPath: '/bin/sh',

[gingerbenw]

Hi @thorbenprimke, thanks for raising this one - I'm glad the plugin is working otherwise!

Could I confirm what your eas build command looks like, and which directory you are running it from? Are you hoisting the dependencies for your expo app?

Thanks!

[thorbenprimke]

Sure.

Commend: STAGE=production eas build --profile production --platform ios --auto-submit

I run this from the folder: /Users/thorben/projects/backstage-app/packages/expo.
The node_modules folder is at the project root: /Users/thorben/projects/backstage-app/

I believe the answer is yes to are you hoisting the dependencies. It is set up as workspaces in the root package.json and all dependencies are installed at the root but defined in the expo folder's package.json.

Let me know if I can provide anything else or you want to me to test a change.

[gingerbenw]

Hi @thorbenprimke - Apologies for the delay on this, could you please try the following:

Install @bugsnag/source-maps as a dev dependency to your expo application, and add the following to the package.json (also in the expo app):

"workspaces": {
    "nohoist": [
      "@bugsnag/plugin-expo-eas-sourcemaps",
      "@bugsnag/source-maps"
    ]
  }

This will prevent the dependencies being hoisted, and allow the plugin to execute the necessary binaries from the node_modules.

[evelant]

@gingerbenw That won't work for people running modern yarn. nohoist only works on yarn classic (1.x versions).

[gingerbenw]

Hi @evelant! Apologies for the slow response, I needed to do some homework on this one.

nohoist works when using the node modules plugin which is required when using expo with yarn 2 and above.

we're looking to automate adding this nohoist option in our CLI shortly.

[evelant]

@gingerbenw Unfortunately it's not that simple.

IIRC when I went though this with yarn (it is confusing!) I found out that won't do it either. I'm pretty sure nohoist does not work with when using nodeLinker: node-modules. There is no way to do per-package hoisting in yarn v2+.

You first have to add nodeLinker: node-modules which turns off "plug n' play" mode to give you a node_modules folder again. Then if you add nohoist to your package.json it will not do anything as it's only supported in yarn v1. In v2+ the only option is install config hoisting limits.

Unfortunately with installConfig: { hoistingLimits: "" } the only options are none (hoist everything) dependencies (hoist everything except direct dependencies) and workspaces (don't hoist anything inside a workspace, treat it as if it were not a workspace).

I have no idea why the yarn team decided to remove per-package hoisting control. It makes things significantly more difficult.

Personally I've moved on to https://pnpm.io as it's far more consistent, fast, configurable, and reliable. Pnpm works well with react-native if you use @rnx-kit/metro-resolver-symlinks to work around metro's 5+ years unresolved lack of symlink support 🤦

[gingerbenw]

Thanks for the useful breakdown @evelant! I think I had misunderstood what was going on in my local testing as I had hoistingLimits: "workspace" set as well as using nohoist.

I wonder whether the best thing to do would be to symlink the necessary dependencies into node_modules in a similar fashion to the expo-yarn-workspaces plugin... 🤔

[evelant]

@gingerbenw I think the way a lot of packages and gradle scripts are doing it now is to use node to resolve the path, such as node --print require.resolve('react-native/package.json') although that assumes node is available on $PATH. That has the benefit of (mostly, looking at you metro) resolving files in the same way all the other tools in the stack are doing it.

[gingerbenw]

After some consideration we’re going to include installConfig.hoistingLimits on our CLI and documentation to get this functional for yarn 2+ in the short term and I will include making our source map upload compatible with hoisting for consideration on our roadmap.

[johnkiely1]

Just to let you know we have released the short term changes mentioned above as of v45.1.2 (for Expo 45) and v46.0.1 (for Expo 46) and updated the documentation to match https://docs.bugsnag.com/platforms/react-native/expo/manual-setup/#eas-build