Why not the node Feature installs the latest nvm by default?

[eitsupi]

Related to #190 and #194

Currently the default version of nvm is fixed at 10 months old 0.39.2 and does not appear to auto-detect the latest version.

features/src/node/devcontainer-feature.json

Lines 31 to 35 in 71ac202

	"nvmVersion": {
	"type": "string",
	"default": "0.39.2",
	"description": "Version of NVM to install."
	}

Do you think we can automatically select the latest version here as is done in a smattering of other Features?

[samruddhikhandale]

Hi 👋

Thanks for raising this question!

By looking at the history of this Feature (especially when it was scripts), it seems like the nvm version has been pinned since the beginning. The only reason I could think of --> Pinning the NVM version helps avoid failures to the Node Feature with an upstream breaking or an error prone version of nvm. This is a good thing to have, however, the Feature ends up having stale NVM installed and it's adds maintenance cost. Also, with the switch to Features, if the upstream nvm breaks, one can always pin the older working version with nvmVersion option or the devcontainers/maintainers can temporarily pin the default to the working version.

Said that, I agree that supporting the latest version as default for nvmVersion makes sense to me! 👍

// cc Chuck Lantz (@Chuxel) joshspicer feel free to share your thoughts or correct my understanding