Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not installing if project react version >= 17.0.1 #793

Closed
therezacuet opened this issue Jun 8, 2021 · 11 comments
Closed

Not installing if project react version >= 17.0.1 #793

therezacuet opened this issue Jun 8, 2021 · 11 comments
Labels

Comments

@therezacuet
Copy link

I tried to install this package on my project but I got a conflict error for react version. Do you have any plan to upgrade peer dependency version?

@therezacuet therezacuet added the bug label Jun 8, 2021
@kishanbharda
Copy link

I have also an error while installing this library in my latest react-native project.

My project configuration :

"react": "17.0.1",
"react-native": "0.64.2",

This is the error that I am gettings :
Screenshot 2021-06-10 at 4 58 36 PM

@donelli
Copy link

donelli commented Jun 10, 2021

Same error here!

@hellotoby
Copy link

You can solve this by running npm install --legacy-peer-deps

@kishanbharda
Copy link

Thank @hellotoby

Installing this package with --legacy-peer-deps solved my problem. I have installed with below command and it installed :

npm install react-native-fast-image --legacy-peer-deps --save

Does the package install this way, can create any other issues?

@Desintegrator
Copy link

+1

@Desintegrator
Copy link

Desintegrator commented Jun 15, 2021

@hellotoby @kishanbharda is package working this way?

@therezacuet
Copy link
Author

@Desintegrator yes this package working this way.

@dcx86
Copy link

dcx86 commented Jun 22, 2021

Fix the upstream dependency conflict, or retry
this command with --force, or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

Running npm install react-native-fast-image --legacy-peer-deps --save will not solve the potentially broken dependency resolution it will just ignore them.

Do you have any plan to upgrade peer dependency version?

@DEVfancybear
Copy link

+1

1 similar comment
@sanduluca
Copy link

+1

@naitikgohain
Copy link

Issue fixed in #790 merge, and the fix is in version 8.3.5 as per #790 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

10 participants