NVM pre-installed on macOS only? #25885
-
I’ve started migrating a workflow from TravisCI to GitHub actions. The workflow is for a node.js app, and the repo includes an On TravisCI (where
Unfortunately I can’t do a similar thing in GitHub actions, because (as per the software in virtual environments page) it seems that From what I understand, in Github Actions the common practice for installing a different Node.js version (than the default pre-installed one) is to use the
Unfortunately,
I’m interested to understand if there was a reason why NVM was picked as a pre-installed option on macOS only, and not on any other environments. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
For what it’s worth, I tried adding an “Install nvm” step into my workflow as follows:
The
The full output of the step is below:
Not entirely sure how to diagnose the “process completed with exit code 3” error? |
Beta Was this translation helpful? Give feedback.
-
nvm is returning error code 3. There’s several reports about this in their issue tracker, in particular, one that sounds relevant describing this behavior when installing nvm while currently in a directory that contains a .nvmrc file. There are some potential workarounds there like passing the |
Beta Was this translation helpful? Give feedback.
-
Thanks @ethomson , I followed your suggestion and was able to get it working with the |
Beta Was this translation helpful? Give feedback.
nvm is returning error code 3. There’s several reports about this in their issue tracker, in particular, one that sounds relevant describing this behavior when installing nvm while currently in a directory that contains a .nvmrc file.
There are some potential workarounds there like passing the
--install
flag.