Comments (24)
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"
},
from standard-version-expo.
"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.
from standard-version-expo.
I got the following while ran 'expo doctor' in SDK 45
Expected package expo-modules-autolinking@~0.8.1 || ~0.9.0 Found invalid: [email protected] (for more info, run: npm why expo-modules-autolinking) Expected package @expo/prebuild-config@^4.0.0 Found invalid: @expo/[email protected] (for more info, run: npm why @expo/prebuild-config)
from standard-version-expo.
Same issue. Using expo 45
Expected package @expo/config-plugins@^4.1.0 Found invalid: @expo/[email protected] (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" },
from standard-version-expo.
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?
from standard-version-expo.
same Issue found on Expo SDK 48 unable to resolved by
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" },
from standard-version-expo.
this library seems abandoned, check out https://github.com/bilwifi/standard-version-expo
from standard-version-expo.
@svdwyer made another fork: https://github.com/mccraveiro/standard-version-expo
from standard-version-expo.
@byCedric can you update the packages so we don't need these work rounds?
from standard-version-expo.
Please add below code to package.json
as temporary workaround
"resolutions": {
"standard-version-expo/**/@expo/config-plugins": "4.1.0"
},
from standard-version-expo.
Same issue on Expo 46:
Expected package @expo/config-plugins@^5.0.0
Found invalid:
@expo/[email protected]
(for more info, run: npm why @expo/config-plugins)
from standard-version-expo.
Expected package expo-modules-autolinking@~0.8.1 || ~0.9.0 Found invalid: [email protected] [email protected] (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.
from standard-version-expo.
Same issue. Using expo 45
Expected package @expo/config-plugins@^4.1.0 Found invalid: @expo/[email protected] (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
from standard-version-expo.
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...
from standard-version-expo.
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??
from standard-version-expo.
Same issue here
Expected package @expo/config-plugins@^5.0.0 Found invalid: @expo/[email protected]
from standard-version-expo.
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/[email protected]" message - And removing the package expo-update enterily, fixed the gradlew compilation issue
from standard-version-expo.
I just tried this resolution, and it might work?
"standard-version-expo/**/@expo/config": "~7.0.2"
from standard-version-expo.
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?
from standard-version-expo.
+1 this is an issue for us after updating to expo 47. should we migrate away from this package or do you intend to update it @byCedric
from standard-version-expo.
also experiencing this issue with expo 47. still looking for a solution, thx-
from standard-version-expo.
same Issue found on Expo SDK 48 unable to resolved by
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" },
Exactly! Am try to upgrade to Expo 48, It doesn't work for me
from standard-version-expo.
@svdwyer that version seems abandoned as well.
from standard-version-expo.
"overrides" with "npm" inside the "package.json" file worked for me with Expo SDK 48
{
"scripts": {
},
"dependencies": {
"expo": "~48.0.18",
"react": "18.2.0",
"react-native": "0.71.8"
},
"overrides": {
"expo-modules-autolinking": "~1.1.0",
"@expo/config-plugins": "~6.0.0",
"@expo/prebuild-config": "~6.0.0"
}
}
Don't forget to remove the "node_modules" files and also the "package-lock.json" before "npm install"
from standard-version-expo.
Related Issues (15)
- Android versionCode bumped to semver? HOT 10
- Android increments are wrong when using prereleases HOT 4
- Add support for `app.config.js` HOT 5
- Supporting `beta`? HOT 1
- Missing getenv dependency after upgrading to Expo 38.0.8
- Android converted to semver despite configs & iOS removes leading zeros in semver HOT 2
- "Manifest must include a JSON object." HOT 7
- [Discussion] How handle test versions and releases HOT 2
- Not matched value between console and execute result.
- Supporting the `expo prebuild` workflow HOT 1
- Bumping version in app.json to package.json version HOT 6
- Please merge the dependabot PRs :) HOT 1
- Get sdkVersion from expo package.json HOT 3
- Add version bumpers for bare projects HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from standard-version-expo.