Update @expo/config dependency to satisfy expo doctor

[GregAtFramework]

Old version

The package depends on"@expo/config": ^3.1.2 which leads to the follow warning when running expo doctor (on a Expo 45 project).

Expected package @expo/config-plugins@^4.1.0
Found invalid:
  @expo/config-plugins@1.0.33

New version

No error when running expo doctor.

[troZee]

Please add below code to package.json as temporary workaround

  "resolutions": {
    "standard-version-expo/**/@expo/config-plugins": "4.1.0"
  },

[TowhidKashem]

"standard-version-expo/**/@expo/config-plugins": "4.1.0"

I'm experiencing the same issue and this didn't work for me. I re-ran yarn install as well after adding that resolution entry but same error.

[NxsHbb]

I got the following while ran 'expo doctor' in SDK 45

Expected package expo-modules-autolinking@~0.8.1 || ~0.9.0 Found invalid: expo-modules-autolinking@0.5.5 (for more info, run: npm why expo-modules-autolinking) Expected package @expo/prebuild-config@^4.0.0 Found invalid: @expo/prebuild-config@3.1.2 (for more info, run: npm why @expo/prebuild-config)

[gtwilliams03]

Same issue on Expo 46:

Expected package @expo/config-plugins@^5.0.0
Found invalid:
  @expo/config-plugins@1.0.33
  (for more info, run: npm why @expo/config-plugins)

[josephadah]

Expected package expo-modules-autolinking@~0.8.1 || ~0.9.0 Found invalid: expo-modules-autolinking@0.8.0 expo-modules-autolinking@0.7.1 (for more info, run: npm why expo-modules-autolinking)
Same issue, not sure if this has anything to do with why my facebook login not working. Redirect to facebook successfully and fails to redirect back to app.

Same issue. Using expo 45
Expected package @expo/config-plugins@^4.1.0 Found invalid: @expo/config-plugins@5.0.1 (for more info, run: npm why @expo/config-plugins)
Adding this to package.json (and re-installling modules) did not work:
"resolutions": { "standard-version-expo/**/@expo/config-plugins": "4.1.0" },

Same issue. Using expo 45 Expected package @expo/config-plugins@^4.1.0 Found invalid: @expo/config-plugins@5.0.1 (for more info, run: npm why @expo/config-plugins) Adding this to package.json (and re-installling modules) did not work: "resolutions": { "standard-version-expo/**/@expo/config-plugins": "4.1.0" },

Upgraded to Expo 46 and removed "resolutions" from package.json. Expo doctor no longer shows any issues

[andreasciamanna]

I'm already in Expo 46. I even went through an expo upgrade 46 and let Expo update any package it can recognize.

The suggested workaround does not work for me.

Shouldn't @expo/config-plugins and @expo/json-file be defined as peer-dependencies?

[jimmihagenTrifecta]

I'm already in Expo 46. I even went through an expo upgrade 46 and let Expo update any package it can recognize.

The suggested workaround does not work for me.

Shouldn't @expo/config-plugins and @expo/json-file be defined as peer-dependencies?

Same situation here, @expo/prebuild-config, @expo/config-plugins and expo-modules-autolinking are all referenced by expo doctor, but not resolved by it.

Does this cause any issues? I have done some EAS builds that seem to work fine on device...

[AdeelKahan]

I create new project with Expo 46 and install some dependencies. after run expo doctor it show fix @expo/prebuild-config, @expo/config-plugins and expo-modules-autolinking these modules. I try to update those modules bit they can't update
and still throw same issue.
Is Expo 46 stable??

[nembi-solutions]

Same issue here

Expected package @expo/config-plugins@^5.0.0 Found invalid: @expo/config-plugins@3.1.0

[nembi-solutions]

In our case,

• Updating the package jest-expo from "jest-expo": "^43.0.1", to `"jest-expo": `"^46.0.1", fix the "Found invalid: @expo/config-plugins@3.1.0" message
• And removing the package expo-update enterily, fixed the gradlew compilation issue

[dan-online]

I was able to fix this long ago by adding this to the package.json:

 "resolutions": {
    "@expo/config-plugins": "~5.0.1",
    "@expo/prebuild-config": "~5.0.3",
    "expo-modules-autolinking": "0.10.3"
  },

[ariccio]

I just tried this resolution, and it might work?

"standard-version-expo/**/@expo/config": "~7.0.2"

[connorpmullins]

This seems to be a real problem. This project uses two functions exposed by @expo/config in version 3, getExpoSDKVersion, and AppJSONConfig. Neither of those functions exist in major version 6 of @expo/config.

For all of you who are manually modifying the version of expo/config that gets resolved, I think you likely are breaking this package. Not in a fatal way, if it's working for you, but yeah. That seems to be what's up.

@byCedric - are there any plans to update this package?