run-node caches the path with nvm version of Node.js that set as default when run-node first runs.
Right now run-node ignores a stale ~/.node_path only when node is not found, but there are other cases to consider:
-
A new version of Node.js was installed and set as default via nvm.
run-nodewill continue to run the old version because the path in.node_pathis not updated. -
A new version of Node.js was installed and set as default via nvm, and the old version is deleted.
run-nodewill not run the new version, and will runnodefound further in the path (like one installed via Homebrew).
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too