-
-
Notifications
You must be signed in to change notification settings - Fork 258
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
Stopped working in react-native-web #731
Comments
Guten Tag, Hans here! 🍻 It looks like you are experiencing an issue after updating to version 3.x.x, but we need more information to help you better. Please provide relevant logs from your runtime environment. For example, if you are using Xcode for iOS, you can find the logs in the Xcode logs window. For Android, please use Once you have that information, we'll be able to assist you more effectively. If you want to support the project and get quicker attention on issues, consider becoming a sponsor on GitHub. It helps a lot!
|
It's standard react-native-web |
@gituser8796 I haven't booted my project in a couple weeks but this was working in web the when I last used it, what version of the library are you using and what version of react native? For Reference I checked my project, RN 0.74.2 |
@amutsch - I'm using react-native@0.75.1 and react-native-mmkv@3.02 In order to get web working I have to manually set react-native-mmkv@2.12.2 (which prevents mobile form loading) Thank you! |
@gituser8796 That means you are not using react native new architecture. 3.x.x only works with new architecture enabled in react native. This is working as designed according to the documentation that @mrousavy has with the release. |
I upgraded my project tonight to 75.2 and mmkv 3.0.2, my android build was working on my windows machine, I will build and test my web, ios and android from my mac when I get back on Sunday |
i got "Identifier 'module' has already been declared", a line before |
I have everything working just fine. Webpack is spitting out some warnings due to how turbomodules need to be defined but it is not preventing starting or using the web side. Following best practice for a major upgrade of my main libs I cleared my node_modules and yarn.lock file as well. Everything is working as I expect it to. Hope this helps but not seeing any issues in my setup. Kicking off my CICD on my update here shortly, I've gone from 74.x and version 2.12.0 to new arch with 3.0.6-beta to 75.2 |
hi @amutsch any progress on this one? it's becoming an issue for use to use this repo - so any fix would be appreciated! |
@gituser8796 I'm going to need more details as all you are providing is a reference Error. I outlined what versions I used at 74 and 75 and before and after new arch and everything is working for me. As I mentioned react-native-web is now required to use 3.x lib(it wasn't with 2.x) but other than some startup warnings everything is working fine on my side, What relevant lib versions are you using(RN, RNWeb, Webpack/vite/other) Compiling this to working web opens up a whole new suite of items to check. Can your create a small reproduction scenario independent of your app? Is your app available to public on github, if so I can take a look there too. |
Are you guys using expo or react-native cli? I am trying to look into this issue, created a a new expo project and it seems like it is working, if you could provide a reproduction repo, I'd be happy to look into it more |
Thanks for all your help guys 🙏🖤 |
@mrousavy no feedback for over a month, I think we can close this, both myself and ISnowFoxl have verified working with expo and RN-cli with RN-web |
awesome thank you! |
This error should be exported by the ESM method used on the react-native-web side, such as the vite used. TurboModuleRegistry does not exist on the react-native-web side, so in
This method can be used temporarily, but I think a better method may be needed. |
Uncaught ReferenceError: exports is not defined
It was working perfectly before 3.x.x
The text was updated successfully, but these errors were encountered: