ReactNative for Windows (vnext)
current subdirectory adds support for an earlier
react-native-windows implementation built in C#. It reimplemented the JS<->Native bridge in C#, and shared the JS with Facebook's implementation of
react-native. The ongoing direction of
react-native involves a closer interaction between C++ and JS which is hard to achieve with a separate C# implementation.
vnext sub-folder, we are working on a rewrite of
react-native-windows built in C++ that reuses the C++ core bridge implementation from Facebook’s React Native. This will allow React Native for Windows to innovate and provide features by sharing the same core as Facebook’s React Native. See Status for more details.
Status and roadmap
vnext package currently supports
v0.58 of corresponding
react-native major version. See releases for more information on
vnext release strategy.
React Native already has great documentation, and we're working to ensure the React Native Windows is part of that documentation story. Check out the React documentation for further details about the React API in general.
Coming soon - we will be publishing more documentation including some of the following shortly:
- A live document that captures the ongoing parity status of this
vnextimplementation with Android and iOS.
- Guides on how to extend native Windows capabilties in C# and C++ using
If you encounter a bug with the React Native Windows C++ implementation or have a feature request, we would like to hear about it. Search the existing issues and try to make sure your problem doesn’t already exist before opening a new issue. It’s helpful if you include the version of Windows, React Native, React Native Windows plugin, and device family (i.e., desktop, Xbox, etc.) you’re using. Please include a stack trace and reduced repro case when appropriate, too.
Please make sure to use the correct template for issues related to the vnext
See Contributing guidelines for how to setup your fork of the repo and start a PR to contribute to React Native Windows C++.