Where do we stand with Turbomodules?

[shamilovtim]

Are Turbomodules on the roadmap for this project or should we lean on react-native-turbo-starter indefinitely? My understanding is that react-native-turbo-starter is not backwards compatible with NativeModules but it's not clear which starter project to contribute to at the moment. To add to the confusion I've heard that Swift support will need to be deprecated for Turbomodules so things are a bit confusing right now for this library.

[satya164]

We just added experimental turbo module support with both backward compatibility and without. Currently, only Obj-C and Java are supported for Turbo modules, and Kotlin support will follow.

If you have time, please test it and lemme know if there are any problems or things to be fixed.

[shamilovtim]

@satya164 I will test ASAP. Thank you for all that you do.

[jacobarvidsson]

@satya164 is this suppose to work for fabric components as well? When I switch the turbo module to a fabric component the build stops working with:

Undefined symbols for architecture arm64:
  "nameOfComponent", referenced from:
      _RCTThirdPartyFabricComponentsProvider in libReact-Codegen.a(RCTThirdPartyFabricComponentsProvider.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

[satya164]

I've only tested with turbo modules for now

[satya164]

Fabric progress: #273