Hi everyone I'm having stuck terminal and worst case frozen computer when I ran:
react-native start
I want to run my android application but I'm blocked by.
React Native version:
System:
OS: macOS 10.14.5
CPU: (4) x64 Intel(R) Core(TM) i5-4570R CPU @ 2.70GHz
Memory: 1.74 GB / 8.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 12.6.0 - /usr/local/bin/node
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
Android SDK:
API Levels: 25, 26, 27, 28
Build Tools: 28.0.3, 29.0.1
System Images: android-27 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5692245
Xcode: /undefined - /usr/bin/xcodebuild
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.4 => 0.60.4
npmGlobalPackages:
create-react-native-app: 2.0.2
react-native-cli: 2.0.1
Follow: https://facebook.github.io/react-native/docs/getting-started
Run in terminal
react-native start
Describe what you expected to happen:
Run my app!
Snack, code example, screenshot, or link to a repository:

I found the solution maybe you need to specify a version of node over here:
https://facebook.github.io/react-native/docs/getting-started#node-watchman-jdk
I just did:
sudo npm install -g n
sudo n 10.16.0
Then works.
Indeed, calling react-native start with RN 0.60.4 and Node.js 12.6 eats several gigs of RAM and takes ages to display _done_.
But with Node.js 10.16 it works like a charm!
Thanks @cbedoy for the hint 馃憣
It did once on my computer when I updated from 0.59 to 0.60. Since then, it runs quickly as it seems only the first launch after the upgrade has more work.
@victorlevasseur It's because the first run generates a cache, which is used for the next runs.
Try react-native start --reset-cache and you'll see the difference.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.
Most helpful comment
Indeed, calling
react-native startwith RN 0.60.4 and Node.js 12.6 eats several gigs of RAM and takes ages to display _done_.But with Node.js 10.16 it works like a charm!
Thanks @cbedoy for the hint 馃憣