-
Notifications
You must be signed in to change notification settings - Fork 25k
Closed
Labels
PartnerResolution: FixedA PR that fixes this issue has been merged.A PR that fixes this issue has been merged.p: MicrosoftPartner: MicrosoftPartner: Microsoft💻CLI
Description
Description
On latest nightlies (example: 0.76.0-nightly-20240715-2eb7bcb8d), the react-native command fails silently without a word as to why.
I understand this is part of the effort to decouple @react-native-community/cli from react-native, but the current implementation breaks for all users.
Anyone having written scripts in package.json like below:
{
"scripts": {
"start": "react-native start"
}
}… or have custom scripts and/or build pipelines that rely on the react-native command, will start seeing failures.
We should keep proxying react-native commands to @react-native-community/cli to avoid breaking current users.
Steps to reproduce
n/a
React Native Version
0.76.0-nightly-20240715-2eb7bcb8d
Affected Platforms
Build - MacOS, Build - Windows, Build - Linux
Output of npx react-native info
n/a
Stacktrace or Logs
n/a
Reproducer
n/a
Screenshots and Videos
No response
cortinico
Metadata
Metadata
Assignees
Labels
PartnerResolution: FixedA PR that fixes this issue has been merged.A PR that fixes this issue has been merged.p: MicrosoftPartner: MicrosoftPartner: Microsoft💻CLI