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
{{ message }}
This repository has been archived by the owner on Jun 10, 2018. It is now read-only.
When using NVM having a system node package installed on Debian or Ubuntu, execjs always uses the system node. This is because it looks for the nodejs binary first, which is provided by the system binary and not NVM (since it is something introduced by the distribution).
Suggestion: first look for node, then nodejs. Or don't look for nodejs at all (unless an env variable is set).
When using NVM having a system node package installed on Debian or Ubuntu, execjs always uses the system node. This is because it looks for the
nodejs
binary first, which is provided by the system binary and not NVM (since it is something introduced by the distribution).Suggestion: first look for
node
, thennodejs
. Or don't look fornodejs
at all (unless an env variable is set).First brought up in NVM: nvm-sh/nvm#308 (comment)
The text was updated successfully, but these errors were encountered: