Closed nibblesnbits closed 1 year ago
I forced this resolution, and I've not noticed any ill effects just yet -- seems to work just fine. For anyone else using Expo/EAS, I used a .npmrc
file in the root of my project to force the installation:
force=true
I tried it using yarn and it working for me
I forced this resolution, and I've not noticed any ill effects just yet -- seems to work just fine. For anyone else using Expo/EAS, I used a
.npmrc
file in the root of my project to force the installation:force=true
It's worth noting, that this approach is global and may cause issues with other packages.
Update: it looks like #918 is working towards this.
I can confirm that forcing react 18 is working without any apparent issues at the moment. With yarn you can set the resolution in your package.json
"resolutions": {
"react": "18.2.0",
"@types/react": "~18.0.17",
"@types/react-native": "~0.69.5"
}
alternatively only force the fast image version to match, but I like to have only a single version in my project.
I've updated the peer dependency. Thank you for the report!
Describe the bug I can't use this module after upgrading to React 18 (RN 0.69.x) because it specifies a dependency on
react@"^16.8.6 || ^17.0.0"
To Reproduce
npm i react-native-fast-image
Expected behavior Installation should succeed.
Dependency versions
If I force this resolution, are there any known issues?