Is there a way to use >=18.16.0 in .nvmrc file?

[OnkarRuikar]

We want to enforce >=18.16.0 because our code is facing issues with prior versions. The string >=18.16.0 doesn't work in .nvmrc file. Nvm throws >=18.16.0 version not found error.

Closest solution is to use lts/hydrogen. At the moment it installs v18.17.1. But this forces/nags users with v18.16.0 to upgrade. How can we handle the situation in .nvmrc file? Is there a way to configure >=18.16.0 condition?

[ljharb]

no, we don’t support that - everything in nvm resolves to one single version.

generally I’d expect everyone in an org to be on the exact same version - not just in a range. Why wouldn’t you want everyone on the latest 18?

[OnkarRuikar]

@ljharb thanks for the clarification!

Why wouldn’t you want everyone on the latest 18?

Because it's an open source project and all contributors are not on same node versions.

[ljharb]

@OnkarRuikar sure but in that case you’d want your contributors to have every supported version installed anyways, which includes 18.17.

[Josh-Cena]

@ljharb Thanks for the pointer; I was trying to make this not an XY problem. For the context I was the one that first complained that >=18.16.0 does not work. For me, I personally don't care if I need to install a new version every time, but I don't want versions to pile up, and nvm migrate and >=18.16.0 will both fix this for me.

[ljharb]

The discussion in #1091 explains why the primary use case of nvm is in fact to have versions "pile up", so you can easily switch between multiple versions, and it's just not optimized for using it as a moving target of a single node version.