Create-react-native-app: npm start hangs on - "Starting packager..."

Created on 16 Oct 2017 · 4Comments · Source: expo/create-react-native-app

Description

When i run yarn start it get stuck with a messagem Starting packager...

Expected Behavior

Run yarn start and the packager starts

Observed Behavior

The packager hangs indefinitely

C:\Users\weslley.rocha\Documents\Projects\React-native\expo\swype3>yarn start
yarn run v1.1.0
$ react-native-scripts start
15:08:32: Starting packager...
15:20:37: Stopping packager...
15:20:37: Packager stopped.
Done in 725.66s.

Environment

Please run these commands in the project folder and fill in their results:

npm ls react-native-scripts:

[email protected] C:\Users\weslley.rocha\Documents\Projects\React-nativeexpo\swype3
`-- [email protected]

npm ls react-native:

[email protected] C:\Users\weslley.rocha\Documents\Projects\React-nativeexpo\swype3
`-- [email protected]

npm ls expo:

[email protected] C:\Users\weslley.rocha\Documents\Projects\React-nativeexpo\swype3
`-- [email protected]

node -v:

v8.2.1

npm -v:

4.6.1

yarn --version:

1.1.0

watchman version:

'watchman' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.

Also specify:

Operating system: Windows 7 x64
Phone/emulator/simulator & version: Genymotion

Source

WeslleyNasRocha

Most helpful comment

Duplicate of #343

You can try this:

echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_user_watches && echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_queued_events && echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_user_instances && echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

If it's still stuck, then install watchman from here and do this

watchman watch-del-all && watchman shutdown-server

dhruvdutt on 25 Oct 2017

👍10

All 4 comments

If i run react-native start it goes:

Scanning 768 folders for symlinks in C:\Users\weslley.rocha\Documents\Projects\React-native\expo\swype3\node_modul
es (18ms)
 ┌────────────────────────────────────────────────────────────────────────────┐
 │  Running packager on port 8081.                                            │
 │                                                                            │
 │  Keep this packager running while developing on any JS projects. Feel      │
 │  free to close this tab and run your own packager instance if you          │
 │  prefer.                                                                   │
 │                                                                            │
 │  https://github.com/facebook/react-native                                  │
 │                                                                            │
 └────────────────────────────────────────────────────────────────────────────┘
Looking for JS files in
   C:\Users\weslley.rocha\Documents\Projects\React-native\expo\swype3


React packager ready.

Loading dependency graph...

But no expo...

WeslleyNasRocha on 16 Oct 2017

Hi, I solved this problem by looking at this page: https://github.com/facebook/react-native/issues/10188#issuecomment-251677161.

by Google Tradutor ;D

HigoRibeiro on 17 Oct 2017

Duplicate of #343

You can try this:

echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_user_watches && echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_queued_events && echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_user_instances && echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

If it's still stuck, then install watchman from here and do this

watchman watch-del-all && watchman shutdown-server

dhruvdutt on 25 Oct 2017

👍10

Hi I am getting the same problem. I created a test app, I was able to work with it using Expo, but now when I run npm start it gets stuck at "Starting Packager..."
react-native info returns this:

Environment:
OS: macOS High Sierra 10.13.5
Node: 8.11.3
Yarn: 1.7.0
npm: 6.1.0
Watchman: 4.9.4
Xcode: Not Found
Android Studio: 3.0 AI-171.4443003

Packages: (wanted => installed)
react: 16.0.0-alpha.12 => 16.0.0-alpha.12
react-native: ^0.55.4 => 0.55.4

When I run npm start --verbose I got this output:

sudo npm start --verbose
npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'start',
npm verb cli '--verbose' ]
npm info using [email protected]
npm info using [email protected]
npm verb run-script [ 'prestart', 'start', 'poststart' ]
npm info lifecycle [email protected]~prestart: [email protected]
npm info lifecycle [email protected]~start: [email protected]

[email protected] start /Users/borch/Documents/React_Native/pet-tracker
react-native-scripts start

22:24:25: Starting packager...
ERROR STARTING PACKAGER
No issue with doctor-watchman-version
No issue with doctor-problem-checking-watchman-version
No issue with doctor-both-app-and-exp-json
No issue with doctor-schema-validation
No issue with doctor-validate-asset-fields
No issue with doctor-schema-validation-exception
No issue with doctor-unversioned
No issue with doctor-versions-endpoint-failed
No issue with doctor-invalid-sdk-version
No issue with doctor-node-modules-missing
No issue with doctor-react-native-not-installed
Starting Metro Bundler on port 19001.
Metro Bundler ready.

jest-haste-map: @providesModule naming collision:
Duplicate module name: crud
Paths: /Users/borch/Documents/React_Native/pet-tracker/awsmobilejs/backend/cloud-api/itemsHandler/package.json collides with /Users/borch/Documents/React_Native/pet-tracker/awsmobilejs/#current-backend-info/cloud-api/itemsHandler/package.json

This warning is caused by a @providesModule declaration with the same name across two different files.
22:28:52: Stopping packager...
22:28:52: Packager stopped.
npm verb lifecycle [email protected]~start: unsafe-perm in lifecycle true
npm verb lifecycle [email protected]~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/borch/Documents/React_Native/pet-tracker/node_modules/.bin:/Users/borch/Documents/platform-tools:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/bin:/usr/local/cuda/bin:/Users/borch/anaconda3/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Users/borch/bin:/Users/borch/Documents/Robotica/esp/xtensa-esp32-elf/bin
npm verb lifecycle [email protected]~start: CWD: /Users/borch/Documents/React_Native/pet-tracker
npm info lifecycle [email protected]~poststart: [email protected]
npm verb exit [ 0, true ]
npm timing npm Completed in 267308ms
npm info ok