expo-doctor showing error from bugsnag dependency

[VicFrolov]

Describe the bug

The key issue appears to be:

@expo/config-plugins@8.0.11 dev peer
node_modules/@expo/config-plugins
  @expo/config-plugins@"~8.0.8" from @expo/config@9.0.4
  node_modules/@expo/config
    peer @expo/config@"^9.0.1" from @bugsnag/plugin-expo-eas-sourcemaps@52.0.0

The problem is coming from @bugsnag/plugin-expo-eas-sourcemaps@52.0.0 which has a peer dependency on an older version of @expo/config (^9.0.1).

Steps to reproduce

1. Start new expo 52 project, add bugsnag via cli tool
2. run npx expo-doctor@latest to see error

Environment

• Bugsnag version: 52
• Expo SDK version (e.g. SDK 44): 52
• Device (e.g. iphonex): iPhone X

Example Repo

• Create a minimal repository that can reproduce the issue
• Link to it here:

Example code snippet

// deps
"@bugsnag/expo": "^52.0.0",

// dev deps
"@bugsnag/plugin-expo-eas-sourcemaps": "^52.0.0",
"@bugsnag/source-maps": "^2.3.3",

Error messages:

Detailed check results:

Expected package @expo/config-plugins@~9.0.0
Found invalid:
  @expo/config-plugins@8.0.11
  (for more info, run: npm why @expo/config-plugins)
Advice: Upgrade dependencies that are using the invalid package versions.

[agrzegorzewski]

Hi @VicFrolov,

Thanks for reaching out.

Unfortunately, we were unable to reproduce this issue when running expo-doctor in a similar project. Creating a fresh Expo 52 project and adding BugSnag does not throw any errors about the @expo/config dependency.

Could you please try reinstalling all of the offending dependencies? If that does not solve the issue, could you please share your package.json and package-lock.json files? In case you’re not comfortable sharing them in a public GitHub thread, please reach out to us at support@bugsnag.com.

[ronb54]

I'm on a similar expo SDK version as @VicFrolov at v52. Installing @bugsnag/source-maps fails:

> npm install --save-dev @bugsnag/source-maps
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: my-app@1.0.0
npm error Found: @expo/config@10.0.8
npm error node_modules/@expo/config
npm error   @expo/config@"^10.0.8" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @expo/config@"^9.0.1" from @bugsnag/plugin-expo-eas-sourcemaps@52.0.0
npm error node_modules/@bugsnag/plugin-expo-eas-sourcemaps
npm error   dev @bugsnag/plugin-expo-eas-sourcemaps@"^52.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error

I just looked at https://github.com/bugsnag/bugsnag-expo/blob/v52/next/packages/plugin-expo-eas-sourcemaps/package.json

Shouldn't @expo/config here be set to 10.0.8?

[enagorny]

It is possible to use npm overrides. Add this to your package.json:

  "overrides": {
    "@expo/config": "~10.0.8"
  },

But agree ideally bugsnag team update it in the repo