Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

rnpm-plugin-windows

Microsoft31.5kMIT0.6.1

rnpm plugin that generates a Windows template project

rnpm, react-native, react-native-windows, rnpm windows

readme

RNPM Plugin for Universal Windows

To bootstrap the creation of Windows projects for React Native, we've published rnpm-plugin-windows. The purpose of this plugin is to provide project init functionality comparable to react-native init and react-native android, and to allow users to build and run React Windows applications from the command line.

Project Initialization

To start, make sure you have the react-native CLI installed globally.

npm install -g react-native-cli

Once the CLI is installed, install rnpm-plugin-windows and initialize your project. Note: if you have Yarn installed, the react-native-cli will prefer to use that instead of npm, so use yarn to install rnpm-plugin-windows.

npm install --save-dev rnpm-plugin-windows
react-native windows

The windows command will do the following:

  • Install react-native-windows from NPM
  • Read the name of your project from package.json
  • Use Yeoman to generate the Windows project files.

Usage

react-native windows [name] [--namespace <namespace>] [--windowsVersion <version>]

The windows command takes an optional command line argument.

  • name - The name of the project, which will be used for both file names and the name of the component that is registered in the React Native AppRegistry. Default value is the name given in the root-level package.json.

The windows command accepts two optional flags.

  • --namepace - The namespace that will be used in the generated native C# code. Default value is name.
  • --windowsVersion - The version of react-native-windows that will be used. Default value is matches the major and minor version of react-native if installed, otherwise the latest version.

React Native 0.27.* -> 0.30.*

For versions of react-native prior to 0.31.0, you'll need to use the rnpm global CLI to run the windows command. Since the RNPM plugin syntax for the react-native CLI is not backward compatibile with rnpm, you'll need to use an older version of rnpm-plugin-windows:

npm install --save-dev rnpm-plugin-windows@0.1.*

Running React Windows Applications

Once react-native-windows is installed in your project, an additional RNPM plugin for running Windows apps is exposed to the react-native-cli. To deploy your app to Desktop, execute:

react-native run-windows

For more information on the kinds of options and flags available for deploying to devices and emulators, use the --help flag to get the command usage information.

changelog

Change Log - rnpm-plugin-windows

This log was last generated on Wed, 25 Mar 2020 20:04:52 GMT and should not be manually modified.

0.6.1

Wed, 25 Mar 2020 20:04:52 GMT

Patches

Minor changes

  • Teach React Native CLI about master and 0.61 versions (ngerlem@microsoft.com)

    0.5.1-0

    Tue, 11 Feb 2020 01:21:44 GMT

Changes

Minor changes

Patches

  • CLI detect project name from app.json (licanhua@live.com)

    0.3.8

    Wed, 06 Nov 2019 13:58:14 GMT

Patches

  • This change enables consuming JSI implementations where the referenced JSI headers differs from the JSI headers in react-native. (anandrag@microsoft.com)

    0.3.7

    Thu, 17 Oct 2019 20:58:22 GMT

Patches

  • Fix two issues: 1) you cannot animated 2 subchannels of the same property with different animations. to fix this we animated yet another property set for translation and scale owned by the props nodes and use one animation to animate all of the subchannels for the uiElement. 2) Reference parameter names which started with a multi digit number are unsupported so i added an n to the start of each name, which was previously just the node's tag. (stpete@microsoft.com)

    0.3.6

    Tue, 15 Oct 2019 13:59:27 GMT

Patches

  • Updates logic for wpf command to install correct dependency (erozell@outlook.com)

    0.3.5

    Tue, 01 Oct 2019 18:17:42 GMT

Patches

  • The customer provided examples revealed a few of issues. One, we were dubble counding the starting value of animatiosn in some cases. Two we were incorrectly relying on JS to tell us to flatten our animated values. Three we were detaching the expression animations that tied the property to the UIElement and in certain cases the JS thread does not inform us that we need to rebuild this cuppling. There is an open issue with this final part #3280 (stpete@microsoft.com)

    0.3.0

    Sat, 28 Sep 2019 01:21:33 GMT

Minor changes

  • add support for cpp (email not defined)

    0.2.13

    Tue, 24 Sep 2019 19:11:20 GMT

Patches