-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 compatible RN 0.43? #54
Comments
@XavierColombel That's because RN 0.43 uses React version Note that we haven't tested compatibility with RN 0.43 since it hasn't been officially released yet. My guess is that it should work flawlessly though. You should just ignore npm warnings, try the plugin, and get back to me if it doesn't work. |
@bd-arc Ok I see what you mean. I've created a brand new project and I've added react-native-snap-carousel only, in order to test it. It doesn't work with RN 0.43 (see the red screen) that has been officially released yesterday I think. I think you can find more about addons here facebook/react#9207 |
@XavierColombel Thanks for the link (you should edit it by the way, since it redirects to a 404 error page ;-). Here is what seems to be the plan for the
Still, I don't like that part:
The issue is that |
@bd-arc I just updated the link! ;) Ok, so I wait for a RN 0.43 compatible version. Thanks for your help. |
Which version of |
@gaearon With RN 0.43, by default:
|
And which versions of addons? |
(Can you double check their |
Chiming in kind of late, but here's a bit more context: As you've noticed, We wanted to update the version of react used inside of react-native and so we needed to also update to a newer release of That being said, you shouldn't be seeing the reference to |
@bvaughn Thank you very much for the detailed information! I appreciate that. I'll make the necessary adjustments to our plugin. Since |
No problem! 😄
|
@XavierColombel Issue should be resolved with version 2.1.1. Can you try and confirm? |
@bd-arc You rock! Thank you so much! |
I've got these errors:
The text was updated successfully, but these errors were encountered: