React-native-windows: react-native windows not working

Created on 23 Jan 2020 · 4Comments · Source: microsoft/react-native-windows

run latest

$ react-native windows
Reading application name from package.json...
Reading react-native version from node_modules...
What version of react-native-windows would you like to install?  Choose one of:  legacy, latest [default]:
legacy
Checking for react-native-windows version matching 0.61.*...
Could not find [email protected].*. Latest version of react-native-windows is 0.59.0-legacy.1, try switching to [email protected].*.

run regacy

$ react-native windows
Reading application name from package.json...
Reading react-native version from node_modules...
What version of react-native-windows would you like to install?  Choose one of:  legacy, latest [default]:
latest
Checking for react-native-windows version matching 0.61.*...
Could not find [email protected].*. Latest version of react-native-windows is 0.59.0-legacy.1, try switching to [email protected].*.

not working?

Author Feedback question

Source

fs-kanayama

Most helpful comment

It indeed does not work out of the box.
The solution is to implicitly declare the version of latest available package:
npx react-native windows --windowsVersion 0.61.0-beta.8

kirill-zhukov on 25 Mar 2020

👍2

All 4 comments

@fs-kanayama The newest available react-native-windows current version is 0.59 (and vnext 0.60), even if 0.60@current was planned for fall 2019. There is an open issue about the roadmap of react-native-windows here: https://github.com/microsoft/react-native-windows/issues/2815

@harinikmsft Can you please take a look at https://github.com/microsoft/react-native-windows/issues/2815 and update the roadmap and etas or forward this to someone who can? We would also welcome an eta for 0.61.

leoek on 23 Jan 2020

@fs-kanayama When you did your react-native init what version did you supply? Doing legacy (aka current) only supports 59 as stated above. Currently the CLI tool does help you with the supported version.

@kmelmon as an FYI if you want to make the error message better and/or include version support.

chrisglein on 23 Jan 2020

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 14 days of this comment.

msftbot[bot] on 30 Jan 2020

It indeed does not work out of the box.
The solution is to implicitly declare the version of latest available package:
npx react-native windows --windowsVersion 0.61.0-beta.8

kirill-zhukov on 25 Mar 2020

👍2

Was this page helpful?

0 / 5 - 0 ratings