node version 6.11.1 is not available

[gtallen1187]

Apologies in advance if this is an easy solve, I'm very much an amateur/rookie when it comes to programming.

I've followed all of your steps for the deployment via now, but the build is failing with the below error message:

> WARN! Requested node version 6.11.1 is not available
> Using Node.js 8.11.3 (default)
> https://slackin-upzeewswgi.now.sh [in clipboard] (bru1) [5s]
> Building…
> ▲ yarn
> yarn install v1.7.0
> info No lockfile found.
> [1/5] Validating package.json...
> error slackin@0.14.0: The engine "node" is incompatible with this module. Expected version "6.11.1".
> info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
> error Found incompatible module
> Error! Build failed

Any help/advice from anyone here would be extremely appreciated.

[avikivity]

Changing "6.11.1" to "6.x.x" in package.json worked for me.

[shawwn]

@avikivity Thanks, that was amazingly helpful in tracking down the problem. There was one other issue I was running into: When attempting to deploy with now, the hostname was being set to a bogus random name, so I had to hardcode hostname to 0.0.0.0.

I've submitted both @avikivity's solution and the hostname hack to PR #382.

In the meantime, if anyone just wants to get slackin to work, run this:

now shawwn/slackin

I've confirmed that works with the latest now client on OS X.

[brycereynolds]

The above still wasn't working for me. I ended up removing the entire node engine declaration from package.json and let now choose. So far so good...

[gtallen1187]

I should have responded earlier - Unfortunately, changing "6.11.1" to "6.x.x" didn't work for me. Different error messages, but the deployments still failed. I'll try removing the node engine declaration from `package.json` and see what happens. Thanks Bryce and @avikivity for your help. Greg Allen gtallen1187@gmail.com (504) 913-6002

…

On Tue, Aug 28, 2018 at 9:42 PM Bryce Reynolds ***@***.***> wrote: The above still wasn't working for me. I ended up removing the entire node engine declaration from package.json and let now choose. So far so good... — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#379 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEfpQAJjKQHx1QeuJo9Uronif-pyeVrbks5uVfGdgaJpZM4WA8x9> .

[lpatmo]

Running now shawwn/slackin unfortunately also did not work for me.

I had to input API keys twice (same when I ran now rauchg/slackin, and I got this error log:

> Using Node.js 6.14.3 (requested: `6.x.x`)
> https://slackin-nxvtrgwvmn.now.sh [in clipboard] (sfo1) [984ms]
> Building…
> ▲ yarn
> yarn install v1.9.4
> info No lockfile found.
> [1/5] Validating package.json...
> error slackin@0.14.0: The engine "node" is incompatible with this module. Expected version "6.x.x".
> error Found incompatible module
> info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
> Error! Build failed```

[distalx]

I guess, there is a PR for this #382.

[shawwn]

@lpatmo try now shawwn/slackin.

rauchg seems to have largely abandoned slack, moving Zeit off their platform and onto spectrum. It's frustrating that they broke one of the prime reasons to use their software. slackin was what got me into Zeit.

[lpatmo]

@shawwn Thanks for the info; I didn't know Zeit was moved to Spectrum! Running now shawwn/slackin unfortunately also did not work for me. The error log I pasted in the above comment is from shawwn/slackin, not from rauchg.

[r39132]

@shawwn
Running now shawwn/slackin results in
```> Using Node.js 6.14.3 (requested: 6.x.x)

https://slackin-tfuzcnplzy.now.sh [in clipboard] (sfo1) [2s]
Building…
▲ yarn
yarn install v1.9.4
info No lockfile found.
error slackin@0.14.0: The engine "node" is incompatible with this module. Expected version "6.x.x".
error Found incompatible module
[1/5] Validating package.json...
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Error! Build failed```

[r39132]

@gtallen1187 @avikivity Did you find a solution? I'm not a node guy, so don't know how to proceed? If I remove the engines line from the package.json file, what do I do next?

[chitacan]

use >= 6.0 in "engines" field, works for me

"engines" : {
  "node": ">= 6.0"
}

alternatively, the error message The engine "node" is incompatible with this module. Expected version "6.x.x". is complaint by yarn. just include package-lock.json in your deployment, now will use npm. (no complaint )