create-react-native-app: Error in trying to run demo app

Description

I am following the instructions to run the sample app. It fails both using an Android and IOS device with the same error.

Observed Behavior

Error

If there’s an error message, please paste the full terminal output and error message in this code block:

9:51:53 PM: (node:13992) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection
olveError: Unable to resolve module `@expo/vector-icons/glyphmaps/Entypo.json` from `C:\react\my-
xpo\vector-icons\Entypo.js`: Module does not exist in the module map or in these directories:
  C:\react\my-project\node_modules\@expo\vector-icons\node_modules\@expo\vector-icons\glyphmaps
,   C:\react\my-project\node_modules\@expo\vector-icons\glyphmaps

This might be related to https://github.com/facebook/react-native/issues/4968
To resolve try the following:
  1. Clear watchman watches: `watchman watch-del-all`.
  2. Delete the `node_modules` folder: `rm -rf node_modules && npm install`.
  3. Reset packager cache: `rm -fr $TMPDIR/react-*` or `npm start --reset-cache`.

Environment

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

  • npm ls react-native-scripts:-- react-native-scripts@0.0.22
  • npm ls react-native:-- react-native@0.42.3
  • npm ls expo:-- react-native@0.42.3
  • node -v:v7.7.4
  • npm -v:4.1.2
  • yarn -v:v0.21.3

Also specify:

  1. Operating system: Windows 8.1
  2. Phone/emulator/simulator & version: IOS 10,2, Samsung Tab 3 running KitKat.

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 22 (7 by maintainers)

Most upvoted comments

Installing watchman didn’t really help.

Not a permanent solution, but this is what got me going again.

rm -rf node_modules/ yarn.lock package-lock.json && npm install

this was a bug with babel-plugin-module-resolver and it was… ahem. resolved.

you must install watchman

npm install -g watchman

it works for me

macos also exists the problems:(

I’m still getting this with Expo 16.0 - thread on it here, apparently an issue with babel-preset-expo. https://github.com/tleunen/babel-plugin-module-resolver/issues/167