Ryann Graham

@jasongin I was just about to open a new issue asking for `nvs use system` when I saw this one.

There is an unfortunate side effect of the `alias` route on systems that have their "system" `node` in a common path such as `/usr/local/bin` as would be the case for...

I'm still trying to wrap my head around how aliases work in `nvs`. My experience is no doubt being coloured by: 1. coming from `nvm` 2. using multiple remotes right...

Current status: ```js const versionRegex = /^(([\w\-]+)\/)?((v?(\d+(\.\d+(\.\d+)?)?(-[0-9A-Za-z.]+)?))|([a-z][a-z_\-][0-9a-z_\-]*))(\/((x86)|(32)|((x)?64)|(arm\w*)|(ppc\w*)))?$/i; ``` 😭

RegExp shock aside, #39 is what I eventually settled on as an implementation of this.

For my own uses, the main advantage of generated code with strong typing would be in the removal of most of the reflection overhead. Considering how much of the code...

> In my personal tests, the reflection overhead didn't come anywhere near the cost of disk access, even with SSDs or running against /dev/shm. In my own code I've had...

Sorry, I completely missed the notification for this :-( @alexwhitman the use of `444` for the permissions was inspired by how `git` stores its content-address objects under `.git/objects/**`. I suspect...

@alexwhitman another option might be to take a look at the [Job Cacher Plugins](https://wiki.jenkins.io/display/JENKINS/Job+Cacher+Plugin), which doesn't bother overwriting files if they already exist, which is appropriate behaviour for cacache.

After opening this it started feeling annoyingly familiar.. then I re-discovered the npmconf module I used to use and see it was deprecated and the functionality rolled back in. Now...