You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 22, 2019. It is now read-only.
Hey there! 👋
Stumbled into this by accident through your dotfiles and I love the concept!
However, I work a lot with node and tend to use different versions of node for different repositories - the older the repo, the older the node version it requires.
It could instead, install something like asdf-vm or nvm (specifically for node) and use these to actually install a specific runtime version.
If you don't care about this kind of versioning - nothing changes, since there will always be just the one version defined in your path.
If you do care about this kind of versioning - it would add it as part of the machine setup so you would use that when needed.
The text was updated successfully, but these errors were encountered:
Hey there! 👋
Stumbled into this by accident through your dotfiles and I love the concept!
However, I work a lot with node and tend to use different versions of node for different repositories - the older the repo, the older the node version it requires.
It would be great if instead of actually installing a specific version here
https://github.com/caarlos0/machine/blob/cc759d87f50102bd698932525bebb2d97924d73c/tasks/node.yml#L3-L6
It could instead, install something like
asdf-vm
ornvm
(specifically for node) and use these to actually install a specific runtime version.If you don't care about this kind of versioning - nothing changes, since there will always be just the one version defined in your path.
If you do care about this kind of versioning - it would add it as part of the machine setup so you would use that when needed.
The text was updated successfully, but these errors were encountered: