Skip to content
Branch: master
Find file History
Office VSTS Default Agent
Office VSTS Default Agent Applying package update to 0.59.0-vnext.90
Latest commit f3b0f2b Jul 16, 2019
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
Chakra Add JSI Unit Tests (#2677) Jul 4, 2019
Desktop.DLL Applying package update to 0.59.0-vnext.90 Jul 16, 2019
Desktop.IntegrationTests Verify format of cpp/h files during CI (#2739) Jul 8, 2019
Desktop.UnitTests Verify format of cpp/h files during CI (#2739) Jul 8, 2019
Desktop Verify format of cpp/h files during CI (#2739) Jul 8, 2019
Folly Reduce source files in Shared items project. (#2708) Jul 1, 2019
FollyWin32 Reduce source files in Shared items project. (#2708) Jul 1, 2019
IntegrationTestScripts Enforce correct platform toolset (#2709) Jul 1, 2019
IntegrationTests introduce focus safe habor for new focus/blur implementation (#2706) Jul 5, 2019
JSI.Desktop.UnitTests Verify format of cpp/h files during CI (#2739) Jul 8, 2019
Playground Enforce correct platform toolset (#2709) Jul 1, 2019
PropertySheets Add JSI Unit Tests (#2677) Jul 4, 2019
ReactCommon Verify format of cpp/h files during CI (#2739) Jul 8, 2019
ReactUWP Applying package update to 0.59.0-vnext.90 Jul 16, 2019
ReactWindowsCore Verify format of cpp/h files during CI (#2739) Jul 8, 2019
Scripts Remove pre/post install hooks (#2771) Jul 16, 2019
Shared Update CMake build def Jul 2, 2019
Universal.IntegrationTests Verify format of cpp/h files during CI (#2739) Jul 8, 2019
Universal.SampleApp Updated SampleApp to have drop-down of available sample apps already … Jul 15, 2019
Universal.UnitTests clang-format: add rule for pch.h and generated files (#2767) Jul 15, 2019
V8Inspector Update target version to 19h1 and set XamlRoot for Flyout (#2456) Jun 10, 2019
docs Add JSI Unit Tests (#2677) Jul 4, 2019
include implement keyboard code (#2734) Jul 10, 2019
jest Hook up some basic formatting configuration for vscode (#2655) Jul 1, 2019
local-cli Hook up some basic formatting configuration for vscode (#2655) Jul 1, 2019
proposals Commiting proposal process files (#2571) Jun 6, 2019
src update AppTheme stub for non-windows (#2763) Jul 12, 2019
stubs Verify format of cpp/h files during CI (#2739) Jul 8, 2019
.editorconfig Enforce correct platform toolset (#2709) Jul 1, 2019
.eslintignore Consolidate built files into Libraries folder (#2727) Jul 3, 2019
.eslintrc.js Hook up some basic formatting configuration for vscode (#2655) Jul 1, 2019
.gitignore Consolidate built files into Libraries folder (#2727) Jul 3, 2019
.npmignore Cleanup various files from the npm package (#2646) Jul 8, 2019
CMakeLists.txt Remove UTs from CMake builds Jun 21, 2019
CopyHeaders.inc Add option for native promise support in Chakra JSI (#2461) May 14, 2019
Directory.Build.props Clean up MSBuild files (#2664) Jun 24, 2019
Directory.Build.targets Clean up MSBuild files (#2664) Jun 24, 2019
NuGet.Config Add documentation for WebSocket types. (#2662) Jun 28, 2019
README.md Update readme Jul 8, 2019
ReactUwp.nuspec Add commit Id to nuget packages (#2647) Jun 21, 2019
ReactWin32.nuspec Add commit Id to nuget packages (#2647) Jun 21, 2019
ReactWindows-TestNuspec.bat Create a seperate uwp nuget (#2516) May 22, 2019
ReactWindows-UWP.sln Implementing 'list' and 'listitem' accessibilityRoles (#2743) Jul 9, 2019
ReactWindows.sln Add JSI Unit Tests (#2677) Jul 4, 2019
index.js Consolidate built files into Libraries folder (#2727) Jul 3, 2019
index.uwp.js Consolidate built files into Libraries folder (#2727) Jul 3, 2019
just-task.js Fix RNTester bundle (#2728) Jul 3, 2019
layoutFilesForNuget.bat Cleanup various files from the npm package (#2646) Jul 8, 2019
makewinrt.inc Minimize use of NOJSC macro (#2670) Jun 25, 2019
package.json Applying package update to 0.59.0-vnext.90 Jul 16, 2019
rn-cli.config.js Consolidate built files into Libraries folder (#2727) Jul 3, 2019
tsconfig.json Consolidate built files into Libraries folder (#2727) Jul 3, 2019
yarn.lock Remove pre/post install hooks (#2771) Jul 16, 2019

README.md

ReactNative for Windows (vnext)

Hero Image with Logo

See the official React Native website for an introduction to React Native. See main landing page for more details on overall direction of react-native-windows.

The 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.

In this 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

The development of the React Native Windows vnext implementation is ongoing. You can take a look at Milestones and Projects for a view on the work streams and tasks.

The vnext package currently supports v0.59 of corresponding react-native major version. See releases for more information on vnext release strategy.

Documentation

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.

For a live document for information on parity status with Android and iOS, including details on implemented and missing components and modules, along with related issues for missing features from partial implementations, see Parity Status.

Coming soon - we will be publishing more documentation including some of the following shortly:

  • Guides on how to extend native Windows capabilties in C# and C++ using vnext

Getting Started

See Getting Started Guide for React Native Windows C++.

Opening issues

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 react-native-windows implementation.

Contributing

See Contributing guidelines for how to setup your fork of the repo and start a PR to contribute to React Native Windows vNext.

You can’t perform that action at this time.