config-plugins Error during "Run expo doctor"

I don’t have a dependency on @config-plugins but when expo doctor runs it throws the following error.

Should I add config-plugins^4.1.5 to my dependencies?

Adding this to package.json seems to have worked. Not sure when I should remove it though. :confused:

"resolutions": {
  "@expo/config-plugins": "^4.1.0"
},

in the warning message notice that it suggests using npm why - this command will let you know which package you are using that brings in an old version of the config plugins package

yeah @notbrent, the same thing here since a few days ago (but I didn’t give importance to it),

❯ yarn workspace @ambito-dolar/client expo doctor
βœ” Found all copies of expo-modules-autolinking
  All copies of expo-modules-autolinking satisfy ~0.8.1 || ~0.9.0
βœ” Found all copies of @expo/config-plugins
Expected package @expo/config-plugins@^4.1.0
Found invalid:
  @expo/config-plugins@5.0.0
  @expo/config-plugins@5.0.0
  @expo/config-plugins@5.0.0
  (for more info, run: npm why @expo/config-plugins)
βœ” Found all copies of @expo/prebuild-config
  All copies of @expo/prebuild-config satisfy ^4.0.0

I did a run of yarn why:

❯ yarn why @expo/config-plugins                                          
β”œβ”€ @config-plugins/react-native-quick-actions@npm:2.0.0
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:~4.1.4)
β”‚
β”œβ”€ @expo/cli@npm:0.1.5
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:~4.1.4)
β”‚
β”œβ”€ @expo/config@npm:6.0.24
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:4.1.5)
β”‚
β”œβ”€ @expo/config@npm:6.0.25
β”‚  └─ @expo/config-plugins@npm:5.0.0 (via npm:~5.0.0)
β”‚
β”œβ”€ @expo/prebuild-config@npm:4.0.3
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:4.1.5)
β”‚
β”œβ”€ expo-dev-client@npm:1.0.0
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:^4.0.14)
β”‚
β”œβ”€ expo-dev-client@npm:1.0.0 [8ec2e]
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:^4.0.14)
β”‚
β”œβ”€ expo-dev-launcher@npm:1.0.0
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:^4.0.14)
β”‚
β”œβ”€ expo-dev-launcher@npm:1.0.0 [3a5c4]
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:^4.0.14)
β”‚
β”œβ”€ expo-dev-menu@npm:1.0.0
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:^4.0.14)
β”‚
β”œβ”€ expo-dev-menu@npm:1.0.0 [3a5c4]
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:^4.0.14)
β”‚
β”œβ”€ expo-file-system@npm:14.0.0
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:^4.0.14)
β”‚
β”œβ”€ expo-file-system@npm:14.0.0 [b3fcf]
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:^4.0.14)
β”‚
β”œβ”€ expo-notifications@npm:0.15.4
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:^4.0.14)
β”‚
β”œβ”€ expo-notifications@npm:0.15.4 [8ec2e]
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:^4.0.14)
β”‚
β”œβ”€ expo-screen-orientation@npm:4.2.0
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:^4.0.14)
β”‚
β”œβ”€ expo-screen-orientation@npm:4.2.0 [8ec2e]
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:^4.0.14)
β”‚
β”œβ”€ expo-system-ui@npm:1.2.0
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:^4.0.14)
β”‚
β”œβ”€ expo-system-ui@npm:1.2.0 [8ec2e]
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:^4.0.14)
β”‚
β”œβ”€ expo-updates@npm:0.13.3
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:^4.0.14)
β”‚
β”œβ”€ expo-updates@npm:0.13.3 [8ec2e]
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:^4.0.14)
β”‚
β”œβ”€ sentry-expo@npm:4.2.0
β”‚  └─ @expo/config-plugins@npm:4.1.5 (via npm:~4.1.4)
β”‚
└─ sentry-expo@npm:4.2.0 [8ec2e]
   └─ @expo/config-plugins@npm:4.1.5 (via npm:~4.1.4)

and if now I do the run for @expo/config (which is the one that 5.0.0 is pointing to) I have the following result:

❯ yarn why @expo/config                    
β”œβ”€ @expo/cli@npm:0.1.5
β”‚  └─ @expo/config@npm:6.0.25 (via npm:~6.0.23)
β”‚
β”œβ”€ @expo/metro-config@npm:0.3.18
β”‚  └─ @expo/config@npm:6.0.24 (via npm:6.0.24)
β”‚
β”œβ”€ @expo/prebuild-config@npm:4.0.3
β”‚  └─ @expo/config@npm:6.0.24 (via npm:6.0.24)
β”‚
β”œβ”€ @expo/webpack-config@npm:0.16.25
β”‚  └─ @expo/config@npm:6.0.24 (via npm:6.0.24)
β”‚
β”œβ”€ expo-constants@npm:13.1.1
β”‚  └─ @expo/config@npm:6.0.25 (via npm:^6.0.14)
β”‚
β”œβ”€ expo-constants@npm:13.1.1 [b3fcf]
β”‚  └─ @expo/config@npm:6.0.25 (via npm:^6.0.14)
β”‚
β”œβ”€ expo-constants@npm:13.1.1 [c7c9d]
β”‚  └─ @expo/config@npm:6.0.25 (via npm:^6.0.14)
β”‚
β”œβ”€ expo-pwa@npm:0.0.120
β”‚  └─ @expo/config@npm:6.0.24 (via npm:6.0.24)
β”‚
β”œβ”€ expo-updates@npm:0.13.3
β”‚  └─ @expo/config@npm:6.0.25 (via npm:^6.0.14)
β”‚
└─ expo-updates@npm:0.13.3 [8ec2e]
   └─ @expo/config@npm:6.0.25 (via npm:^6.0.14)

it would appear that the @expo/config-plugins@5.0.0 version is used by the expo-constants and expo-updates

i can’t reproduce this. i made a new project and ran expo install expo-constants expo-updates and then cleared yarn.lock and node_modules and installed again and i don’t get @expo/config-plugins@5.0.0. can you share a minimal reproducible example?

1 Like

@notbrent I reinstalled all my dependencies and removed the yarn.lock and it’s working right now, over the weekend I had done it several times, and it hadn’t worked, possibly some dependency was causing problems, thanks :heart_hands:

❯ yarn workspace @ambito-dolar/client expo doctor
βœ” Found all copies of expo-modules-autolinking
  All copies of expo-modules-autolinking satisfy ~0.8.1 || ~0.9.0
βœ” Found all copies of @expo/config-plugins
  All copies of @expo/config-plugins satisfy ^4.1.0
βœ” Found all copies of @expo/prebuild-config
  All copies of @expo/prebuild-config satisfy ^4.0.0

πŸŽ‰ Didn't find any issues with the project!

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.