I got an error saying it's an NPM error, maybe it's an expo-cli bug?

What I Wanted to Do

I wanted to play around with React Native using the Expo CLI. I’m new to React Native and Expo. I am familiar with basic concepts of ReactJS as I’ve used it in a recent university course.

I’m using Windows and cygwin64.

As outlined in the React Native page, it says after installing the expo-cli package using NPM, I should run

expo init AwesomeProject

I tried that, but cygwin64 says I have to provide a --template flag as I’m not in the interactive mode. I added the flag, so now my command becomes

expo init AwesomeProject --template blank

Now, cygwin64 says I have to provide a --name flag, and I did. Now my command becomes

expo init --name AwesomeProject --template blank

Finally, it says I have to provide which directory I want to install the files in. Now my command becomes

expo init --name AwesomeProject --template blank dir

The command runs, but its taking too long, so I Ctrl+C and it stops.

I thought everything was fine, until I pressed Enter.

What Happened Instead

There is an error that says it is a problem with NPM itself, hence why I am here.
I’m here to share it because cygwin64 says to “Please report this error at https://npm.community

Reproduction Steps

I interrupted the expo init command by pressing Ctrl+C, and then a bunch of errors comes flying in.

Sorry I couldn’t be more specific. I’m still a university student and I don’t know how to do fancy stuff. I am familiar with git, but I don’t know what to share if I were to create a repo as instructed by these comments.

Details

Here’s the debug file:

2019-04-25T00_12_41_965Z-debug.log (709.1 KB)

Platform Info

$ npm --versions

{ npm: '6.4.1',
  ares: '1.15.0',
  cldr: '33.1',
  http_parser: '2.8.0',
  icu: '62.1',
  modules: '64',
  napi: '3',
  nghttp2: '1.34.0',
  node: '10.15.3',
  openssl: '1.1.0j',
  tz: '2018e',
  unicode: '11.0',
  uv: '1.23.2',
  v8: '6.8.275.32-node.51',
  zlib: '1.2.11' }

$ node -p process.platform

win32

Thanks. The cb() never called! error is not the underlying error, and in theory there should be another displayed as well although I did not see one in your log file. The error reporting was improved in nom v6.6.0, so if upgrading npm is an option you could try that for better diagnostics.

Somebody who knows React might have specific advice.

Glad to be of assistance. Will try, thank you.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.