-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Duplicate versions of react-native being installed #1803
Comments
Came here to post the same issue, looks like it was accidentally added to the dependencies in this commit: 34e2d7a I believe It should be listed as a peerDependency instead |
I've been tearing my hair out over this issue, glad to come across the root of the problem
Removing |
Same issue |
Same here, please update the package |
yeah this has been destroying my day as well. as a quick work around, you can just go delete the dupe of react-native out of the node_modules folder within react-native-router-flux. Ugly, but will at least get you up and running for the time being |
+1 |
reinstall 3.38.0 for now |
It's not related to yarn I believe. Because even if I install it with npm I get the same issue. I deleted my node_modules folder and cleared the npm cache, but the issue was persistent. Currently, I went ahead with a workaround which I read on a GitHub issue where I have to delete the node_modules/react-native-router-flux/node_modules/react-native package. I hope they fix this issue soon. |
same here |
Waiting for the fix I rollback to react-native-router-flux@3.30.1 |
same here |
Got wrecked by this too. Fixed with the rollback to 3.38.0
|
Same by me, had to remove the react-native directory inside react-native-router-flux manually to make things work. |
yep, either rollback or remove the folder manually, thanks for the workarounds |
Hope the problem is resolved in next release. |
same issue, please help to fix |
Rolling back to 3.38.0 fixed the issue for me, thanks a lot guys! |
Same here, back to 3.38.0 fixed it. Thank you! |
+1 |
thanks! |
I'll get the champagne ready! |
Same issue, solved rolling back to 3.38.0 |
Rolling back to v0.38.0 or just deleting the react-native folder inside react-native-router-flux/node_modules/ and also delete symlink to react-native inside react-native-router-flux/node_modules/.bin/ will work for now. |
Posting the above for convenience copy & paste 😄
|
stuck just now,thanks |
+1 |
What worked for me was this sequence: watchman watch-del-all |
Tried all the above steps and the errors went away but the router doesnt and scenes donot render the components. Double checked if they are being fetched properly and they are . Not sure why |
Tried command line's fix and this worked to get my build working without errors but when i run my unit tests with jest its complaining it can not find the node_module folders in the react-native-router-flux folder. Looks like jest is still getting a reference to these folders :( |
@geecurve got the same error and nothing |
@prtkkmrsngh did you delete the react-native folder inside of /node_modules/react-native-router-flux? Or revert to |
@MattyK14 revert to 3.38.0 and upgraded RN to 0.44 |
Please guys, react-native-router-flux@3.38.1 |
@nazaslater fix your version to "react-native-router-flux": "3.38.0", you have 3.38.1 |
Thanks @Tonacatecuhtli |
Its been a month, any chance of making the tiny fix that can end this bug? |
@aksonov please fix issue. 3.39.2 |
😥 |
@abdurrahmanekr @asokol Can we publish this into npm its still showing 3.39.1 as the latest https://www.npmjs.com/package/react-native-router-flux |
it's 3.39.2 now |
react-native-router-flux v3.38.1
react-native v0.42.3
yarn install is causing react-native v0.42.3 and react-native v0.41.1 to be installed
Should react and react-native be installed as a peerDependency for react-native-router-flux?
To repro:
react-native init {projectName} --version=0.42.3
cd {projectName}
yarn add react-native-router-flux
npm start
You should see
yarn add react-native-router-flux@3.38.0
Should succeed
The text was updated successfully, but these errors were encountered: