Open jperry opened 10 years ago
Agreed. I updated by node plugin from 1.0.28 to 1.0.42 and was surprised by the requirement to add a "Node.js NVM Installer" runner step, for my working build configurations that had "Node.js NPM" build runners. I already had created my own method of having a contained NVM/Node.js solution, which I want to continue to use. See also Issue #27.
This feature will also allow to use windows agents with nvm. I guess it'll be easier then installing of windows version of nvm for windows agents. For now I use command line runner to switch node version, which is not a great sollution
@shedar would you like to provide pull request for this?
Is this something that still be supported? Maybe by setting the NVM Home on the agent?
If an agent already has nvm installed use that one instead or at least have the ability to state which one it should use.