You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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-node will continue to run the old version because the path in .node_path is not updated.
A new version of Node.js was installed and set as default via nvm, and the old version is deleted. run-node will not run the new version, and will run node found further in the path (like one installed via Homebrew).
The text was updated successfully, but these errors were encountered:
Happy to consider solutions. I personally neither use nvm nor find it very good. I would recommend https://github.com/tj/n instead. It has no such problem.
run-node
caches the path with nvm version of Node.js that set as default whenrun-node
first runs.Right now
run-node
ignores a stale~/.node_path
only whennode
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-node
will continue to run the old version because the path in.node_path
is not updated.A new version of Node.js was installed and set as default via nvm, and the old version is deleted.
run-node
will not run the new version, and will runnode
found further in the path (like one installed via Homebrew).The text was updated successfully, but these errors were encountered: