RN core in 0.76 will be defaulting new apps to the new architecture. It stands to reason that RNW apps should also switch the default in 0.76. What's the challenge there? Well, the Fabric renderer for RNW remains a work in progress. Core parity is decent but not complete, and more importantly fewer modules are going to be supported in this timeline.
So... why change the default? Because we're talking about new apps, not existing apps. And while there will be bumps for new apps, we'd rather set them on the right path for the future now rather than have them create a Paper app and then have to gut it moving to Fabric in the next version or two. And changing the default does not remove the option to fall back to Paper. If the new arch proves not viable for them, we can instruct them how to switch to Paper.
This issue should track what's needed to make this as good of an experience for everyone as we can.
### Tasks
- [ ] https://github.com/microsoft/react-native-windows/issues/13935
- [ ] https://github.com/microsoft/react-native-windows/issues/13936
- [ ] https://github.com/microsoft/react-native-windows/issues/13459
lin72h, austinhallock, acraftydev and hsjoberg
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4