[Error]: Cannot read property '1' of null

[ghost]

Describe the bug

$ meteor-now
✖ [METEOR-NOW] - TypeError: Cannot read property '1' of null
    at /Users/.nvm/versions/node/v8.12.0/lib/node_modules/meteor-now/build/main.js:388:45
    at Generator.next (<anonymous>)

To Reproduce
Steps to reproduce the behavior:
I have followed this instructions in the setup guide.
I am using node v8.12.0. and meteor [email protected]

Expected behavior
I expect the next prompts to run.

[evolross]

Any particular reason for using a Meteor 1.7.x beta? Have your tried the latest stable Meteor 1.8.x?

[ghost]

Last time I tried 1.8 I was getting this very strange memory leak in production and so I went back to this version and it was stable for me. I can try to give it a shot.

The root of the issue above is that it cannot find the proper METEOR version when I run the meteor-now command. I'm wondering if anyone else has run into this issue or seen this error before.

[frankwo1]

giving me exactly the same error message with meteor 1.7, 1.8 1.8.1
I have also tried specifying Now V1 (in Now.json)- same type-error - but breaks after warning of no MONGO_URL (even tho I did specify with e flag)
ℹ [METEOR-NOW] - Preparing build
⚠ [METEOR-NOW] - WARNING: Did not pass a MONGO_URL. Bundling a NON-PRODUCTION version of MongoDB with your application. Read about the limitations here: https://git.io/vM72E
⚠ [METEOR-NOW] - WARNING: It might take a few minutes for the app to connect to the bundled MongoDB instance after the deployment has completed.
ℹ [METEOR-NOW] - creating supervisord.conf
(node:18603) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): zlib: Cannot read property 'length' of null
(node:18603) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.