Out of the box install doesn't work with Node v7.2.1

[christopher-francisco]

Ran the 3 first commands in the generator page but it fails with the error:

node-pre-gyp ERR! Tried to download(404): https://node-inspector.s3.amazonaws.com/debug/v0.7.7/node-v51-darwin-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for [email protected] and [email protected] (node-v51 ABI) (falling back to source compile with node-gyp)

... more stack trace

Did I miss something?

[theednaffattack]

Not sure if you're still facing this problem, but I had the same error when using Angular-fullstack. To get around I switched node versions from v7.7.1 to node v6.3.1. From what I've seen in the node inspector issues any version older than 6.3.1 should work.

[codydaig]

@chris-fa This project does not support Node 4 yet. If you look at the builds for the main project (github.com/meanjs/mean) you'll see what versions of node that are supported.

[theednaffattack]

@codydaig How can I check something like that? I looked in package.json under "engines" and it states:
"engines": {
"node": ">=6.3.0",
"npm": ">=3.10.8"
}
But that's on master which is v0.5.0 though, right? So if I check the "0.4.x" branch's package.json is that what I'm looking for?

How do I ensure I'm using the right version of the generator with the right version of MeanJS? I'm sorry if these questions are remedial but I've used this package for years now and grown a lot as a dev because of it, but.... I'm still not certain how to find the answer myself.

0.4.x:
"engines": {
"node": ">=0.10.28",
"npm": ">=1.4.28"
}

Is there a better / more conventional place to check?

[codydaig]

Look at the Travis.ci log under the main project to see what node versions are currently passing.
https://github.com/meanjs/mean