-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
[@types/react-navigation] the type definition seems to be broken. #21294
Comments
I'm having a related issue. With a fresh run of
Hopefully this is related and the out of the box bug helps you track it down. |
Flipping hell... I think I've found the source of the issue... For some reason, it seems @types/react rolled back to an earlier version ("^15.6.6") instead of ("^16.0.20") (this version was there yesterday) I don't know how to report that, but manually changing my package.json to use My new dependencies looks like this:
Alternatively, when installing your @types/react indicate the version you want to get |
Just call this two commands:
That will update the react types to the latest version. |
Hi @mamiu, |
@rodrigoelp Yes, you're right. But they fixed it fast. So nevermind! |
Just fire following command:
It works for me. |
Hi @hpdeveloper28, the issue has been fixed for quite a while. Cheers! |
EDIT: Trying to find a solution to my problem, noticed @types/react has been bumped down to 15.6.6, this is given to you when setting up a new project. That is the root cause of this issue. If you know how to report that issue, please link it to this issue and then close it
Hi guys, today I created a new react-native project and got several issues when setting up the project with react-navigation.
I've followed the steps below to set up my project:
These are the dependencies in my sample project
Version 2.6.1
@types/react-navigation
and had the following compilation issues:Mentioning the authors as listed on the index.d.ts file:
@huhuanming, @mhcgrq, @fangpenlin, @abrahambotros, @petejkim @iRoachie, @charlesfamu, @phanalpha, @timwangdev, @BANG88
The text was updated successfully, but these errors were encountered: