We're excited to release our first preview build of react-native-windows 0.67! There have been many changes to both react-native-windows and react-native itself and we would love your feedback on anything that doesn't work as expected.
How to upgrade
You can view the differences between different versions of C++ applications using a special version of React Native Upgrade Helper.
Upgrade helper does not yet support C# projects or projects using experimental features. It is recommended to generate a new project using react-native-windows-init for projects not supported by Upgrade Helper.
What's New
-
View manager pointer hooks: View managers can now implement
IViewManagerWithPointerEventsto customize handling of pointer events that would normally be propagated to React as touch events. -
Accessible images: Images with the
accessibleprop set will now show up to screen readers, including support foraccessibilityLabel. -
Unsigned by default: We previously included a temporary AppX signing certificate when creating a new project. You no longer need to check in a certificate, and only need to use one when publishing your application.
-
RNW version queries: Libraries targetting multiple versions of
react-native-windowscan now specialize behavior dependant on the version of RNW the library is compiled with.RNW_AT_LEASTandRNW_LESS_THANmacros are exposed to C++ community modules targetting RNW 0.67+. -
Bug-fixes and improvements: We've made many more fixes across the platform. Expect less crashes, more correct behavior, and quality of life improvements for developers.
Breaking Changes
- AppX deployment: UWP applications without certificates need to be deployed using loose file registration. This is handled for you if you use Visual studio, or
run-windows, but may require changes if you are using custom logic for deployment.