Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

expo-cli: TypeError: Cannot read property 'compile' of undefined #213

Closed
TheSalarKhan opened this issue Nov 25, 2018 · 81 comments

Comments

Projects
None yet
@TheSalarKhan
Copy link

commented Nov 25, 2018

Description

Expo-cli is crashing on npm start with the error message
[02:46:59] TypeError: Cannot read property 'compile' of undefined

Expected Behavior

  1. install expo-cli using npm install expo-cli -g
  2. start a new project using 'expo init`
  3. Browser pops up with dev tools and a QR code is visible on the terminal.

Observed Behavior

  1. The browser opens up blank
  2. The terminal reads:
msalar@Dranzer:~$ expo init myproj
? Choose a template: blank
[02:57:27] Extracting project files...
[02:57:28] Customizing project...

Your project is ready at /home/msalar/myproj
To get started, you can type:

  cd myproj
  expo start

msalar@Dranzer:~$ cd myproj/
msalar@Dranzer:~/myproj$ npm start

> empty-project-template@ start /home/msalar/myproj
> expo start

[03:01:33] Starting project at /home/msalar/myproj
[03:01:33] Expo DevTools is running at http://localhost:19002
[03:01:33] Opening DevTools in the browser... (press shift-d to disable)
[03:01:37] TypeError: Cannot read property 'compile' of undefined
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! empty-project-template@ start: `expo start`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the empty-project-template@ start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/msalar/.npm/_logs/2018-11-25T22_01_37_331Z-debug.log
msalar@Dranzer:~/myproj$ 

Here's the log file

0 info it worked if it ends with ok
1 verbose cli [ '/home/msalar/.nvm/versions/node/v8.12.0/bin/node',
1 verbose cli   '/home/msalar/.nvm/versions/node/v8.12.0/bin/npm',
1 verbose cli   'start' ]
2 info using npm@6.4.1
3 info using node@v8.12.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle empty-project-template@~prestart: empty-project-template@
6 info lifecycle empty-project-template@~start: empty-project-template@
7 verbose lifecycle empty-project-template@~start: unsafe-perm in lifecycle true
8 verbose lifecycle empty-project-template@~start: PATH: /home/msalar/.nvm/versions/node/v8.12.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/msalar/myproj/node_modules/.bin:/home/msalar/.nvm/versions/node/v8.12.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle empty-project-template@~start: CWD: /home/msalar/myproj
10 silly lifecycle empty-project-template@~start: Args: [ '-c', 'expo start' ]
11 silly lifecycle empty-project-template@~start: Returned: code: 1  signal: null
12 info lifecycle empty-project-template@~start: Failed to exec start script
13 verbose stack Error: empty-project-template@ start: `expo start`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/home/msalar/.nvm/versions/node/v8.12.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at EventEmitter.emit (events.js:214:7)
13 verbose stack     at ChildProcess.<anonymous> (/home/msalar/.nvm/versions/node/v8.12.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at ChildProcess.emit (events.js:214:7)
13 verbose stack     at maybeClose (internal/child_process.js:915:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid empty-project-template@
15 verbose cwd /home/msalar/myproj
16 verbose Linux 4.15.0-29-generic
17 verbose argv "/home/msalar/.nvm/versions/node/v8.12.0/bin/node" "/home/msalar/.nvm/versions/node/v8.12.0/bin/npm" "start"
18 verbose node v8.12.0
19 verbose npm  v6.4.1
20 error code ELIFECYCLE
21 error errno 1
22 error empty-project-template@ start: `expo start`
22 error Exit status 1
23 error Failed at the empty-project-template@ start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Environment

It was giving errors so I set EXPO_DEBUG=true.

msalar@Dranzer:~/myproj$ expo diagnostics
[03:03:48] Generating diagnostics report...
[03:03:48] You can join our slack here: https://slack.expo.io/.

  Expo CLI 2.4.0 environment info:
    System:
      OS: Linux 4.15 Ubuntu 18.04.1 LTS (Bionic Beaver)
      Shell: 4.4.19 - /bin/bash
    Binaries:
      Node: 8.12.0 - ~/.nvm/versions/node/v8.12.0/bin/node
      npm: 6.4.1 - ~/.nvm/versions/node/v8.12.0/bin/npm
    npmPackages:
      expo: ^31.0.2 => 31.0.2 
      react: 16.5.0 => 16.5.0 
      react-native: https://github.com/expo/react-native/archive/sdk-31.0.0.tar.gz => 0.57.1 
    npmGlobalPackages:
      expo-cli: 2.4.0

  Diagnostics report:
/[03:03:50] Request failed with status code 500
[03:03:50] Error: Request failed with status code 500
    at createError (/home/msalar/.nvm/versions/node/v8.12.0/lib/node_modules/expo-cli/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/home/msalar/.nvm/versions/node/v8.12.0/lib/node_modules/expo-cli/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/home/msalar/.nvm/versions/node/v8.12.0/lib/node_modules/expo-cli/node_modules/axios/lib/adapters/http.js:236:11)
    at emitNone (events.js:111:20)
    at IncomingMessage.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)

Reproducible Demo

  1. install expo-cli using npm install expo-cli -g
  2. start a new project using 'expo init`
  3. cd into the project folder and run expo start or npm start
@meatwallace

This comment has been minimized.

Copy link

commented Nov 25, 2018

running publish locally repeatedly i'm hitting no issues at all.

expo diagnostics from my local machine:

  Expo CLI 2.4.0 environment info:
    System:
      OS: macOS High Sierra 10.13.5
      Shell: 5.6.2 - /usr/local/bin/zsh
    Binaries:
      Node: 11.0.0 - ~/.nvm/versions/node/v11.0.0/bin/node
      Yarn: 1.12.1 - /usr/local/bin/yarn
      npm: 6.4.1 - ~/.nvm/versions/node/v11.0.0/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    IDEs:
      Android Studio: 3.1 AI-173.4720617
      Xcode: /undefined - /usr/bin/xcodebuild
    npmPackages:
      expo: 31.0.5 => 31.0.5
      react: 16.6.0-alpha.8af6728 => 16.6.0-alpha.8af6728
      react-native: https://github.com/expo/react-native/archive/sdk-31.0.1.tar.gz => 0.57.1
      react-navigation: 3.0.0 => 3.0.0

  Diagnostics report:
    https://exp-xde-diagnostics.s3.amazonaws.com/lithodomos-eb5107c5-3a70-40fe-b4fe-3e7bc77eec92.tar.gz

looking at the original post, it looks like it threw an error even trying to upload diagnostic reports.

we just hit the same error on 2 deployments jobs in our CI environment, and are running a 3rd time now w/ EXPO_DEBUG enabled - but is this a bug pushed to expo's infrastructure or something? ephemeral routing issue?

@KaizhaoLiang

This comment has been minimized.

Copy link

commented Nov 25, 2018

Is there any temporary fix for this problem? I need to demo my final project for class tmr. Help!!!

@byCedric

This comment has been minimized.

Copy link
Contributor

commented Nov 25, 2018

@KaizhaoLiang I've been able to replicate it on Node 8, but on the latest (Node 11) it just works. Might be something for you to try for your demo...

@smcguffi

This comment has been minimized.

Copy link

commented Nov 25, 2018

@KaizhaoLiang I've been able to replicate it on Node 8, but on the latest (Node 11) it just works. Might be something for you to try for your demo...

I'm on v11.1.0 and still having this issue.

@tarikneradin

This comment has been minimized.

Copy link

commented Nov 25, 2018

I've tried v8.11.3 and v11.2.0, having the same issue.

@meatwallace

This comment has been minimized.

Copy link

commented Nov 25, 2018

@KaizhaoLiang I've been able to replicate it on Node 8, but on the latest (Node 11) it just works. Might be something for you to try for your demo...

running 11.0 locally works, but 11.0 is failing in our CI

@allison-buhler

This comment has been minimized.

Copy link

commented Nov 25, 2018

I'm seeing this issue locally on my Macbook Pro with Node versions 8.9.4, 11.0.0, and 11.2.0. I have not attempted on any other platforms.

@sujithvellat

This comment has been minimized.

Copy link

commented Nov 25, 2018

I was setting up expo on my new laptop and I got the same error on a new project with node v11.2.0.
Here is the diagnostics report

Sujiths-MBP:personal sujithvellat$ expo init
? Choose a project name: MyApp
? Choose a template: blank
[17:47:48] Downloading project files...
[17:47:52] Extracting project files...
[17:47:58] Customizing project...

Your project is ready at /Users/sujithvellat/projects/personal/MyApp
To get started, you can type:

cd MyApp
expo start

Sujiths-MBP:personal sujithvellat$ cd MyApp/
Sujiths-MBP:MyApp sujithvellat$ expo start
[17:48:13] Starting project at /Users/sujithvellat/projects/personal/MyApp
[17:48:14] Expo DevTools is running at http://localhost:19004
[17:48:14] Opening DevTools in the browser... (press shift-d to disable)
[17:48:15] TypeError: Cannot read property 'compile' of undefined
Sujiths-MBP:MyApp sujithvellat$ expo diagnostics
[17:48:43] Generating diagnostics report...
[17:48:43] You can join our slack here: https://slack.expo.io/.

Expo CLI 2.4.0 environment info:
System:
OS: macOS 10.14.1
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 11.2.0 - /usr/local/bin/node
npm: 6.4.1 - /usr/local/bin/npm
IDEs:
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
expo: ^31.0.2 => 31.0.2
react: 16.5.0 => 16.5.0
react-native: https://github.com/expo/react-native/archive/sdk-31.0.0.tar.gz => 0.57.1

Diagnostics report:
https://exp-xde-diagnostics.s3.amazonaws.com/marlabsinnovations-899a40d7-9f17-4512-8901-468fecc390b0.tar.gz

@byCedric

This comment has been minimized.

Copy link
Contributor

commented Nov 25, 2018

I've opened a forum issue, sometimes they respond faster there. https://forums.expo.io/t/new-project-with-expo-cli-crashes/16310.

I can replicate it with both Node 11, and Node 8, even after refreshing my node modules.

@rsmelo92

This comment has been minimized.

Copy link

commented Nov 25, 2018

I'm facing the same issues when creating a new app with expo on 8 and also on 11

@zbaloch

This comment has been minimized.

Copy link

commented Nov 25, 2018

I am also facing the same issue.

[02:18:25] Expo DevTools is running at http://localhost:19002
[02:18:25] Opening DevTools in the browser... (press shift-d to disable)
[02:18:30] TypeError: Cannot read property 'compile' of undefined
@bogdan-calapod

This comment has been minimized.

Copy link

commented Nov 25, 2018

Also facing this and it's driving me nuts - worked perfectly until yesterday.

@bogdan-calapod

This comment has been minimized.

Copy link

commented Nov 25, 2018

I also tried installing webpack-dev-server for what it's worth (saw some older issues related to this) but didn't do anything.

@SunburntRock89

This comment has been minimized.

Copy link

commented Nov 25, 2018

Can repro, Node 10.13.0

@SunburntRock89

This comment has been minimized.

Copy link

commented Nov 25, 2018

Ran with DEBUG=true option, got the following output.
https://gist.github.com/SunburntRock89/250012020cd0cfbd273113688c28b0db

Tried to get diagnostic info but got

D:\Documents\Projects\YT-App>expo diagnostics
[23:42:33] Generating diagnostics report...
[23:42:33] You can join our slack here: https://slack.expo.io/.

  Expo CLI 2.4.0 environment info:
    System:
      OS: Windows 10
    Binaries:
      npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD

  Diagnostics report:
\[23:42:37] Request failed with status code 500
[23:42:37] Error: Request failed with status code 500
    at createError (C:\Users\rhys0\AppData\Roaming\npm\node_modules\expo-cli\node_modules\axios\lib\core\createError.js:16:15)
    at settle (C:\Users\rhys0\AppData\Roaming\npm\node_modules\expo-cli\node_modules\axios\lib\core\settle.js:17:12)
    at IncomingMessage.handleStreamEnd (C:\Users\rhys0\AppData\Roaming\npm\node_modules\expo-cli\node_modules\axios\lib\adapters\http.js:236:11)
    at IncomingMessage.emit (events.js:187:15)
    at endReadableNT (_stream_readable.js:1094:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
@albertstartup

This comment has been minimized.

Copy link

commented Nov 25, 2018

I tried expo-cli@2.0.0 on node 10.11, same problem.

@skyleraustin

This comment has been minimized.

Copy link

commented Nov 25, 2018

Same error - expo-cli 2.1.0 and 2.4.0 on both node 10.4.0 and 11.2.0

@marcosmartini

This comment has been minimized.

Copy link

commented Nov 26, 2018

Same here.
expo-cli 2.3.8 and 2.4.0 on node 8.11.3 on Mac

@Sciscitator

This comment has been minimized.

Copy link

commented Nov 26, 2018

+1

node v10.5.0 and expo 2.4.0 on Macbook Pro

@Kweiza

This comment has been minimized.

Copy link

commented Nov 26, 2018

+1
I tried expo-cli 2.2.0, 2.2.4, 2.3.0 and 2.4.0 and node v8.12.0 on Ubuntu 18.04

@rsimpsonn

This comment has been minimized.

Copy link

commented Nov 26, 2018

+1
node v11.2.0, expo-cli 2.4.0 on Macbook Pro

@dachinat

This comment has been minimized.

Copy link

commented Nov 26, 2018

+1
screen shot 2018-11-26 at 4 10 33 am

@francisdelgad

This comment has been minimized.

Copy link

commented Nov 26, 2018

I'm also experiencing this bug

@guppythegod

This comment has been minimized.

Copy link

commented Nov 26, 2018

I literally came here to create this issue. I'm having the same problem and can't seem to fix it.

@shergea

This comment has been minimized.

Copy link

commented Nov 26, 2018

+1
node v10.13.0, expo-cli 2.4.0 on Windows 10
node v11.2.0, expo-cli 2.4.0 on Macbook Pro

@ScoRoc

This comment has been minimized.

Copy link

commented Nov 26, 2018

+1
had the same error with node v8.9.4. upgraded to v11.2.0 and still got the error.

npm v6.4.1
expo-cli 2.4.0

Macbook Pro

@Cameron1996

This comment has been minimized.

Copy link

commented Nov 26, 2018

Got the same issue, did anyone else get any weird EOF issues before this? Code seemed to be working fine, then EOF issues and while trying to fix that im now no longer able to launch it at all.
For what its worth, it was running the update for expo-cli when i think it stopped altogether, also on a Macbook pro.

@andresmanikis

This comment has been minimized.

Copy link

commented Nov 26, 2018

Same here, node 10.13.0, npm 6.4.1, expo-cli 2.4.0.

Anyway, just took a look at the commits. The latest one was 6 days ago and expo-cli was working yesterday. So I doubt if it is really an expo-cli problem or a problem with one of the dependencies of the project it generates.

@lfernando2091

This comment has been minimized.

Copy link

commented Nov 26, 2018

I have the same error

  • TypeError: Cannot read property 'compile' of undefined
@Snakeyesz

This comment has been minimized.

Copy link

commented Nov 26, 2018

+1
Node: v9.11.1
npm: 6.1.0
Expo-cli: 2.4.0, 2.2.4
OS: Win 10

Was on 2.2.4, updated to 2.4.0, got this error, rolling back to 2.2.4 did not fix it.

@sy92th

This comment has been minimized.

Copy link

commented Nov 26, 2018

Hi everyone, I have encountered this issue when upgrading expo-cli version to 2.4.0
Removing expo-cli and reinstall the old version does not solve this problem

Here's how I solved the problem ( see attachment) :

  • Uninstall the current version and install expo-cli version 2.2.5
  • Delete folder expo-cli in /usr/local/lib/node_modules/ (Location of expo-cli when you install global node module)
  • Download expo-cli from this link (I copied from my friend's computer, he did not upgrade to the new version) and extract to the expo-cli folder ( /usr/local/lib/node_modules/ ).
    https://drive.google.com/file/d/1sIhS-yuLfFliwpds6xv1JaVQGb7PF0L1/view?usp=sharing

This is a temporary solution and we still need to wait for expo-cli to be upgraded to the new version after they fix this.

screen shot 2018-11-26 at 10 18 48

@sislovesmedotcom

This comment has been minimized.

Copy link

commented Nov 26, 2018

+1

[11:18:19] Starting project at /Users/ccis-004/Desktop/Workspace/cashcart-mobile
[11:18:20] Expo DevTools is running at http://localhost:19002
[11:18:20] Opening DevTools in the browser... (press shift-d to disable)
[11:18:40] TypeError: Cannot read property 'compile' of undefined

@twise2

This comment has been minimized.

Copy link

commented Nov 26, 2018

+1

[22:26:18] Starting project at /Users/user/Desktop/app
[22:26:20] Expo DevTools is running at http://localhost:19002
[22:26:20] Opening DevTools in the browser... (press shift-d to disable)
[22:26:25] TypeError: Cannot read property 'compile' of undefined

MacOS Sierra, version 10.12
/usr/local/Cellar/watchman/4.9.0_2/bin/watchman
└── react-native@0.55.4
└── expo-cli@2.2.5

@muadem1992

This comment has been minimized.

Copy link

commented Nov 26, 2018

It worked for me @sy92th

@sislovesmedotcom

This comment has been minimized.

Copy link

commented Nov 26, 2018

Thank you @sy92th 👍

@mhezzet

This comment has been minimized.

Copy link

commented Nov 26, 2018

iam using
https://snack.expo.io/
now

@il10

This comment has been minimized.

Copy link

commented Nov 26, 2018

What is the command to install a specific version for expo?
In this case I am trying to install expo 2.2.5

@sy92th

This comment has been minimized.

Copy link

commented Nov 26, 2018

@il10 What is the command to install a specific version for expo?
npm install -g expo-cli@2.2.5

@AndrewSkinner16

This comment has been minimized.

Copy link

commented Nov 26, 2018

I've uninstalled 4.4 and installed 2.2.5 and still getting the same error...
There is a new version of expo-cli available (2.4.0).
You are currently using expo-cli 2.2.5
Run npm install -g expo-cli to get the latest version
[21:08:14] Starting project at /Users/andrewskinner/Desktop/test_react
[21:08:14] Expo DevTools is running at http://localhost:19002
[21:08:14] Opening DevTools in the browser... (press shift-d to disable)
[21:08:16] TypeError: Cannot read property 'compile' of undefined
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! my-new-project@ start: expo start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the my-new-project@ start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/andrewskinner/.npm/_logs/2018-11-26T05_08_16_674Z-debug.log

@romnycristopher

This comment has been minimized.

Copy link

commented Nov 26, 2018

Worked for me, Thanks @sy92th !

@deeptimoti

This comment has been minimized.

Copy link

commented Nov 26, 2018

I am also having same issue, tried uninstalling the expo-cli but nothing happened.
Did anyone solve this?

@brightidea

This comment has been minimized.

Copy link

commented Nov 26, 2018

still having the same issue even after trying the fixes mentioned above. Had hope for @sy92th's to work but alas no dice.

@udnisap

This comment has been minimized.

Copy link

commented Nov 26, 2018

Full stack trace if anyone wants to dig deaper

VM558 log.js:56 [12:13:29] Starting project at /private/tmp/React-Native/AwesomeProject
VM558 log.js:56 [12:13:29] Expo DevTools is running at http://localhost:19002
VM558 log.js:56 [12:13:29] Opening DevTools in the browser... (press shift-d to disable)
VM558 log.js:84 [12:13:35] TypeError: Cannot read property 'compile' of undefined
consoleError @ VM558 log.js:84
(anonymous) @ VM558 log.js:166
respectProgressBars @ VM558 log.js:94
error @ VM558 log.js:165
_callee$ @ VM85 exp.js:284
tryCatch @ VM160 runtime.js:62
invoke @ VM160 runtime.js:296
prototype.(anonymous function) @ VM160 runtime.js:114
step @ VM86 asyncToGenerator.js:17
(anonymous) @ VM86 asyncToGenerator.js:30
Promise rejected (async)
step @ VM86 asyncToGenerator.js:27
(anonymous) @ VM86 asyncToGenerator.js:28
Promise resolved (async)
step @ VM86 asyncToGenerator.js:27
(anonymous) @ VM86 asyncToGenerator.js:35
F @ VM96 _export.js:36
(anonymous) @ VM86 asyncToGenerator.js:14
(anonymous) @ VM85 exp.js:306
listener @ VM161 index.js:315
emit @ VM21 events.js:180
Command.parseArgs @ VM161 index.js:654
Command.parse @ VM161 index.js:474
runAsync @ VM85 exp.js:654
_callee5$ @ VM85 exp.js:723
tryCatch @ VM160 runtime.js:62
invoke @ VM160 runtime.js:296
prototype.(anonymous function) @ VM160 runtime.js:114
step @ VM86 asyncToGenerator.js:17
(anonymous) @ VM86 asyncToGenerator.js:35
F @ VM96 _export.js:36
(anonymous) @ VM86 asyncToGenerator.js:14
run @ VM85 exp.js:731
(anonymous) @ VM82 expo.js:11
Module._compile @ VM43 loader.js:651
Module._extensions..js @ VM43 loader.js:665
Module.load @ VM43 loader.js:566
tryModuleLoad @ VM43 loader.js:506
Module._load @ VM43 loader.js:498
Module.runMain @ VM43 loader.js:695
startup @ VM20 node.js:201
bootstrapNodeJSCore @ VM20 node.js:516
@ankraj077

This comment has been minimized.

Copy link

commented Nov 26, 2018

Same here

TypeError: Cannot read property 'compile' of undefined

This is so frustrating

Wasting hours of time to solve this types of errors instead of doing some real work on app features.

This is completely demotivating me to work on my stuff. Expo has bunch of such issues. Not good.

@kot-ezhva

This comment has been minimized.

Copy link

commented Nov 26, 2018

2.2.5 is't worked for me.
I tried:
Reinstall yarn
Reinstall expo (yarn global add expo-cli@2.2.5)
Result via expo start:
image
😿

@sjchmiela sjchmiela self-assigned this Nov 26, 2018

@bonham000

This comment has been minimized.

Copy link

commented Nov 26, 2018

Same issue for my, described here (https://forums.expo.io/t/running-start-and-publish-with-expo-cli-throws-typeerror/16310/6).

I get this issue now repeatedly in CI builds, but I can run expo locally without issue. Expo cli version 2.4.0 in both environments. CI is running node 8.11.3 in docker.

A co-worker is having the same failure locally when running expo start.

@sjchmiela

This comment has been minimized.

Copy link
Contributor

commented Nov 26, 2018

Hey all, thank you for your patience and all the proposed workarounds, solutions and explanations! We really appreciate that the community is working hand in hand to help each other while we're asleep. 😅

I was able to reproduce the problem, I'll see what I can do to fix it ASAP! 🙂

@pawel-ogorzalek

This comment has been minimized.

Copy link

commented Nov 26, 2018

Hi, same issue for me. I posted StackOverflow issue yesterday.

@blucell

This comment has been minimized.

Copy link

commented Nov 26, 2018

It seems to be a problem with an update of a dependency, thus reinstalling it causes the problem, because it upgrades its minor versions. After inspection:

node --inspect ~/.config/yarn/global/node_modules/expo-cli/bin/expo.js start

screen shot 2018-11-26 at 11 08 41

Which is in the file ~/.config/yarn/global/node_modules/xdl/node_modules/joi/lib/index.js

@sjchmiela

This comment has been minimized.

Copy link
Contributor

commented Nov 26, 2018

That's right! We've just found this too! joi was upgraded 14 hours ago with version 14.3.0 which produces this issue, we'll publish expo-cli with joi dependency requirement fixed soon. 🙂

@MuhammetAliDere

This comment has been minimized.

Copy link

commented Nov 26, 2018

+1
os: mac high sierra 10.13.4
node: 11.2.0
npm: 6.4.1
expo: 2.4.0
screen shot 2018-11-26 at 12 16 11

@sjchmiela

This comment has been minimized.

Copy link
Contributor

commented Nov 26, 2018

expo-cli@2.4.1 published! A fresh install of expo-cli, i. e.

npm uninstall -g expo-cli && npm i -g expo-cli

solves the issue (I don't know if plain npm i -g expo-cli works too, but it should). 🙂

@incNick

This comment has been minimized.

Copy link

commented Nov 26, 2018

expo-cli@2.4.1 published! A fresh install of expo-cli, i. e.

npm uninstall -g expo-cli && npm i -g expo-cli

solves the issue (I don't know if plain npm i -g expo-cli works too, but it should).

Great~

@TheSalarKhan

This comment has been minimized.

Copy link
Author

commented Nov 26, 2018

expo-cli@2.4.1 published! A fresh install of expo-cli, i. e.

npm uninstall -g expo-cli && npm i -g expo-cli

solves the issue (I don't know if plain npm i -g expo-cli works too, but it should). slightly_smiling_face

Thanks @sjchmiela. I confirm that this now works like a dream. 🙂 🎉

Closing the issue.

@deeptimoti

This comment has been minimized.

Copy link

commented Nov 26, 2018

great!!!! This finally works @

expo-cli@2.4.1 published! A fresh install of expo-cli, i. e.

npm uninstall -g expo-cli && npm i -g expo-cli

solves the issue (I don't know if plain npm i -g expo-cli works too, but it should). 🙂

great!!!! This worked now after lot of hits and trials. :)

@latifuluman

This comment has been minimized.

Copy link

commented Jan 27, 2019

I have encountered with this problem and it is solved by applying the following steps:
rm -rf node_modules
rm yarn.lock
yarn install

@byCedric

This comment has been minimized.

Copy link
Contributor

commented Jan 27, 2019

@latifuluman yes, the issue was related to joi@14.3.0 and expo-cli@2.4.1 (as stated above). After the patch was released in expo-cli@2.4.1, a "clean install" of the CLI was recommended to patch all expo projects and solve the issue.

If you encounter this problem again in all later CLI versions, let us know! 😀 And if so, could you share the version of your expo-cli in a new issue? For now, happy coding! 😁

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.