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
Stacktrace or Logs
Reproducer
n/a
Screenshots and Videos
No response
Description
On latest nightlies (example: 0.76.0-nightly-20240715-2eb7bcb8d), the
react-nativecommand fails silently without a word as to why.I understand this is part of the effort to decouple
@react-native-community/clifromreact-native, but the current implementation breaks for all users.Anyone having written scripts in
package.jsonlike below:{ "scripts": { "start": "react-native start" } }… or have custom scripts and/or build pipelines that rely on the
react-nativecommand, will start seeing failures.We should keep proxying
react-nativecommands to@react-native-community/clito 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 infoStacktrace or Logs
Reproducer
n/a
Screenshots and Videos
No response