Node got busted (I can't boxen good)

[erikjung]

I attempted to update my personal manifest on Friday to make a newer version of Node available for a specific directory. I used this method from the puppet-nodejs docs:

# install a node version
nodejs::version { '0.12.2': }

# ensure a certain node version is used in a dir
nodejs::local { '/path/to/some/project':
  version => '0.12'
}

When running boxen afterwards, I got some massive failures that kept retrying. I had to CTRL + C out of it. I then did a git reset --hard and reran boxen. Seemed to run without any issues (minus the warning about OX S):

--> Preparing to auto-update...
--> Complete! Nothing new from upstream.
--> You must be running one of the following OS X versions: 10.8 10.9 10.10.

Ever since then, any node or npm command I try results in this:

nodenv: version `v0.10' is not installed

So it seems my Node versions got hosed. Not sure what the preferred way is to get them back. :sob:

[erikjung]

Of course, this means anything that uses Node (like gulp) fails hard as well.

[lyzadanger]

This should be fixed now, yes?

[lyzadanger]

@erikjung I think this is resolved by various upstream merges. Your node is solid now, right?

[erikjung]

@lyzadanger Yep!