This fixes RNW@0.61 support and adds support for autolinking on RNW@0.63 and beyond.
react-native-config Windows Implementation
Module Installation
You can either use autolinking on react-native-windows 0.63 and later or manually link the module on earlier realeases.
Automatic install with autolinking on RNW >= 0.63
RNCConfig supports autolinking. Just call: npm i react-native-config --save
Manual installation on RNW >= 0.62
npm install react-native-config --save- Open your solution in Visual Studio 2019 (eg.
windows\yourapp.sln) - Right-click Solution icon in Solution Explorer > Add > Existing Project...
- Add
node_modules\react-native-config\windows\RNCConfig\RNCConfig.vcxproj - Right-click main application project > Add > Reference...
- Select
RNCConfigin Solution Projects - In app
pch.hadd#include "winrt/RNCConfig.h" - In
App.cppaddPackageProviders().Append(winrt::RNCConfig::ReactPackageProvider());beforeInitializeComponent();
Manual installation on RNW 0.61
Do the same steps as for 0.62, but use node_modules\RNCConfig\windows\RNCConfig61\RNCConfig.vcxproj in step 4.
Module development
If you want to contribute to this module Windows implementation, first you must install the Windows Development Dependencies.
You must temporary install react-native-windows package. Versions of react-native-windows and react-native must match. E.g. if the moudule uses react-native@0.62, install npm i react-native-windows@^0.62 --dev.
Now, you will be able to open corresponding RNCConfig...sln file, e.g. RNCConfig62.sln for react-native-windows@0.62.