You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, I refer to the instruction like below which was a pr has been merged #291
Focus areas to test
Testing of this change was performed using a local copy of this branch, Verdaccio to run a local npm proxy, and react-native-macos and react-native-macos-init were published to the local Verdaccio server. Then the intended usage was tested:
$ npx react-native init AwesomeApp
$ cd AwesomeApp
$ npx react-native-macos-init
After installed the verdaccio proxy and push code success
I tried to init my macOS app with npx, but it failed with: command not found: react-native
The text was updated successfully, but these errors were encountered:
Hi @tangkunyin : the issue is because in this fork of react-native, the package.json name is still "name": "react-native" even though it is published to npmjs.org as "react-native-macos". In the build pipeline we run a script to rename the local copy in package.json to "react-native-macos" just prior to npm publish. To work around this issue locally, you have to manually rename your local copy of package.json prior to publishing to verdaccio.
We have this backwards internal naming for legacy reasons. I will be making a PR soon to make the name in package.json "react-native-macos" in the repo.
Hi there, I refer to the instruction like below which was a pr has been merged #291
After installed the verdaccio proxy and push code success

I tried to init my macOS app with npx, but it failed with: command not found: react-native
The text was updated successfully, but these errors were encountered: