engines.node ($node_version)' Įcho 'Reverting to default node version.' Īdd-zsh-hook chpwd load-node-version-from-package-json engines.node is $node_version' Įcho 'This directory has a package.json file with. engines.node version defined' Įlif ] || ] || ] thenĮcho 'nvm does not support special characters (^, >, ~)' Įcho 'No changes applied, please use nvm to set manually' Įcho 'package.json. Local node_version='$(jq -r '.engines.node | select(.!=null)' $package_json_path)'Įcho 'package.json has no.

# Check if $package_json_path file exists. Local package_json_path='$(pwd)/package.json' # If there is not a node version defined with package.json, # Check the current directory for a package.json file You could automate a bit it with custom command in scripts section of package.json, but still it needs to be run somehow (I mean you could try to hack something like git pre-status hook - which on its own doesn't exist - and put it there), but I personally think that every way of using nvm and changing your node for whole OS implicitly is not a good solution.# Add this code to.

Last option is to conditionaly verify output of node -v command and running nvm for you, like other guys said. I didn't have a chance to check it on my own, but looks like exactly what you need. Other way would be to try switching to pnpm and use its use-node-version option, which I've find out recently. It would be kinda a big change in your approach to running project (especially on Windows without wsl), but overall it have many pros and depending where you run it, you could simply just deploy whole image instead of copying files etc. Probably the most reasonable and 'proper' way to do it would be to enclose it in docker images.

Change nvm version