-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
[Vite] [Web] No matching export in RNRenderer.web.js for import "RNRenderer" #6265
Comments
Hey! 👋 The issue doesn't seem to contain a minimal reproduction. Could you provide a snack or a link to a GitHub repository under your username that reproduces the problem? |
Hey ! This issue is also occuring on react native for web devlopment , React Native version : 0.74.3 . Its shows a warning on web page : Is anyone else also facing the same issue ? |
In my setup, this error occures starting version |
But i am developing the native and webapp with react native , when installing the reanimated 3.12.0 mobile app crashes says mismtach between react-native and reanimated versions, also web app got blank and just an empty root div. Using react native 0.74.3 version |
hi, did you find a solution for this problem? I am also facing this issues.. |
Also seeing this issue trying to upgrade to to 3.14.0 (previously using 3.8.1). Seeing it on web
|
I was seeing this error in 3.10.1 and it's gone after upgrading to 3.15.0. I checked the file |
Description
As of 3.13 I believe this error starts to occur in Vite:
Steps to reproduce
Sorry to not have a great repro, but if you create a Vite app and import the latest Reanimated you will see it! Only posting here without full repro because the actual fix is pretty simple!
The file
react-native-reanimated/lib/module/platform-specific/RNRenderer.web.js
doesn't export anything:Which cases Vite to break. Instead, maybe we can export
null
?Snack or a link to a repository
https://github.com/universal-future/vxrn
Reanimated version
3.14.0
React Native version
0.73.1
Platforms
Web
JavaScript runtime
None
Workflow
None
Architecture
None
Build type
None
Device
None
Device model
No response
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: