Replies: 3 comments 4 replies
-
|
Okay so it seems that when they get added to the separate What scenarios could cause the |
Beta Was this translation helpful? Give feedback.
-
|
Actually, after investigating more, it appears that in Obj-C modules, this Except this implementation doesn't even look at the |
Beta Was this translation helpful? Give feedback.
-
|
I was missing something: bridged/legacy-compatible modules use |
Beta Was this translation helpful? Give feedback.
-
|
@Dunedubby thanks for the thorough investigation and I apologize for the delay in answering. Last week we were bus with some internal projects and I could not dedicate a lor of time to Github, sadly. Please consider that the configuration with TurboModule, Fabric and Bridge mode is not supported anymore. We keep providing the possibility to disable bridgeless for debugging purpose, but users are supposed to use the New Architecture as a whole: TurboModule, Fabric and Bridgeless. I'm also a bit concerned in updating the docs with so low level details. You did a great job investigating and diving deep in the code, but those details will change in the future (for example when we approach the removal of the Old Architecture) so writing those down in the docs also mean that we have to keep them updated. Plus, I don't see how much they will benefit the average users who don't need to go in such details to learn and use React Native. What do you think? |
Beta Was this translation helpful? Give feedback.
-
|
That seems fair, thanks for the response. I guess this discussion exists for anyone else searching up how to migrate legacy-compatible libraries to the newest event architecture, so that's probably good enough for now without adding to the docs. Overall we're very impressed by the speed-up and decrease in overhead after switching to fully bridgeless, so I also wanted to express my appreciation for that! |
Beta Was this translation helpful? Give feedback.
-
|
I am trying to understand the principles of React Native. At present, we are just starting to study the communication between JS and Native. The TurboModule System can enable JavaScript and Native to communicate synchronously. My question is, using JSCore's JSCntent can also enable JS and Native to communicate synchronously. What are the differences through JSI? This question may be foolish, but I look forward to your answer. In addition, the new architecture has many concepts that are difficult to understand, but I would like to understand its principles. Do you have any recommended articles |
Beta Was this translation helpful? Give feedback.
-
|
JSI is an abstraction on top of the JS Engine. There are multiple JS engine around: JSCore, maintained by Apple, Hermes, that is the default for React Native and that is developed by Meta and V8, to mention a few of them. Synchronous communication is possible with any of them probably, but JSI allow us to abstract them to a common interface so that we can swap engines without having to change the implementation or the method we call. So, yes, you can achieve the same thing by directly use the JSCore APIs, but then it would not work with Hermes, for example. o understand better the New Architecture, I suggest to:
|
Beta Was this translation helpful? Give feedback.
-
Hi, I'm having a little trouble understanding how the new
EventEmittersare working behind the scenes on iOS, and if there's a disconnect between the documentation and what actually happens. So my understanding is that every function that is created in the JSI module gets ajsi::Value __hostFunction_...function generated in the...-generated.cppfile, as well as avirtualmethod declaration in theSpecJSI.hfile, among other things. Should we expecting similar functions to exist for aonThingHappensJS method, after we declare areadonly onThingHappens: EventEmitter<blah>? Or is there another syntax to call these events on the JS side?Beta Was this translation helpful? Give feedback.
All reactions