Assaf Arkin

NPM treats `engines.node` as advisory, but that's not the only way to use `package.json`. It's actually very convenient when everyone on the team, the CI server, and production servers all...

How do you tell `.nvmrc` to pick the version specified in `package.json`?

That's not what I was asking for. Having multiple files that specify which version of iojs/Node is in use, just means more things breaking because "works on my machine". Common...

If you don't like this feature don't use it. I'd like to have such a feature that I will then choose to use for my projects.

I'm most familiar with https://github.com/stedolan/jq which Heroku uses to parse `package.json` as part their deploy setup. Semver can also solved: https://github.com/heroku/heroku-buildpack-nodejs/blob/master/lib/build.sh#L133 PR would be pointless, we can't even agree that...

https://gist.github.com/assaf/ee377a186371e2e269a7

If you set `engines.node` to `1.6.2` it will call `nvm use v1.6.2`. If you set `engines.iojs` to `1.6.2` it will call `nvm use iojs-v1.6.2`. If you set `engines.node` to 0.12.0...

I don't think it's a good idea to break current behavior. Could be a new command, or use an alias, maybe `nvm use package`?

Alternatively, it could be a path, so `nvm use ` first looks up an alias with that name, if that fails, it looks up a file with that name. That...

No time for that.