Whitney Young

@xinshangshangxin any help you can provide tracking down the cause of this would be appreciated.

@chrisjensen thanks for all the details. Personally, I'm using `n` because of speed related issues.

@NickTikhonov, the determination of a version matching is complex for various reasons. For instance, `8.0` can mean use any patch version for that minor release. Additionally, matching on the node...

@NickTikhonov @ljharb we do an [`nvm list`](https://github.com/wbyoung/avn-nvm/blob/fbaf735d0fab37347a861696090387f54f2446bd/index.js#L135) before doing the `nvm use`. The goal of that code is to return the appropriate command to execute in the shell so that...

Thanks, @ljharb. @nicktikhonov a PR based on this would be welcome and likely address the issues you’re facing.

I thought I commented on this before, but the version matching doesn't necessarily mean that the path (and hence the global modules, compilation flags, etc) are the **best** match. For...

You could have the exact same version installed with both `n` and `nvm`. Which one should be used then? The choice changes which global modules will be used.

Probably start debugging by editing `$HOME/.avn/bin/avn.sh` and commenting out parts of the script until it doesn't fork bomb any more. Could be specific to your config, but also could be...

Can you find an example of another tool that does a better job with figuring out which script file to use based on platform? Something like RVM may be a...

I'm open to the idea of using another field in `package.json` to specify the version. As @ljharb mentions, it shouldn't be the `engines`. But I would want to replace (deprecate)...