-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Can NVS detect package.json's engines.node property ? #184
Comments
|
Yes, as @ljharb pointed out, |
Ours is locked to major version, which makes sense to me for a closed-source binary/frontend where the only node users are also in control of the package.json. I realise it's not really the purpose of |
Along its current behavior detecting
.nvmrc
or.node-version
, it would be nice if nvs could detect as well the engines.node property found in package.jsonI met this usecase quite often among my clients whree they don't use nvmrc or node-version and don't allow me to add these files, but define an explicit engines.node version.
As a result i can't use nvs on a regular basis since i have to type systematically
nvs use <node version required by the project>
each time i use a new shell .... every day.And yes i have tried nvs alias and link, but they don't persist per directory, and i feel a detection mode (like for nvmrc node-version files) sound more appropriate (and direct)
The text was updated successfully, but these errors were encountered: