-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Issue with React Native project #1891
Comments
@bolismauro I just ran into this myself. Removing:
from |
It seems that now those errors are gone. I receive a massive amount of errors from react-native files though. |
Hmm, I don't get those. We may be on different versions of something:
There's actually a 0.26.0 out, Then my
|
I just upgraded to the latest flow, 0.26.0. No, I'm still not seeing react-native errors. |
I'm using RN 0.25.1 since I can't update it to the 0.26 because of a bug. |
Hey! |
Sure,
I changed these
based on @Benjamin-Dobell comment |
I am facing the same issue. |
Make sure you're using a .flowconfig from the version of react-native you're using and install the same version of flow that's mentioned in the [version] section of that .flowconfig |
So this is the structure
I moved flowconfig file in the root folder but nothing has changed. I still have a lot (> 72) errors on react native. I've also tried to change the paths on flowconfig to take into account the react folder but nothing has changed |
I am getting these errors as well.
Below are my versions for various modules:
I tried all the suggestions provided in this issue. Also it's creating problem only in my machine and working fine in others. I assume there is no problem with |
@deeptiagrawa You're definitely not the only one getting this. You are running some out-dated software, but I'm still receiving these same errors every update. I still have to comment out:
in
|
Is anyone else still experiencing these errors? I just upgraded to 0.33 and have many of them:
|
I had the same errors. I changed [libs] pathes to react-native modules and now everything is ok.
|
I'm using a default installation of react-native 0.34.0 and I still see this error. Starting to wonder if it's tied to my machine somehow |
Bump into this error with Ignore these files inside
|
Ran into this with You can see the generated |
For anyone who still needs help with this, I have fixed the issue on my machine: Instead of running flow with
I'm also running RN 0.44.0 and flow-bin 0.42.0 |
Looks like there is a known way to do this now, so I'm going to close the issue. Feel free to object if there's something else here that should be fixed in the flow codebase and I can reopen. |
@asolove What is the known way? I didn't find a solution in this thread. I still get about 50 errors from React Native libraries, like:
|
Also got some errors today with |
I realized the importance of keeping the Flow version in sync with React Native. Check the |
Hello everyone. I'm working on a React Native project and I receive this error every time I (or someone else, like a package in
node_modules
) importreact
.I honestly don't understand what's going on. Has anyone else this problem?
I searched in the past issues and I only find something related to third party libraries, but never to react itself
The text was updated successfully, but these errors were encountered: