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
Suppose you installed both sbt and node in Homebrew, say, under /opt/homebrew/bin. When nodenv is initialized without jenv, the $PATH would be ~/.nodenv/shims/node:/opt/homebrew/bin, therefore node is resolved as ~/.nodenv/shims/node, which is expected.
Unfortunately, when jenv's sbt plugin is enabled, jenv will prepend the path containing sbt to $PATH, which is /opt/homebrew/bin, therefore the $PATH becomes ~/.jenv/versions/10.0/bin:/opt/homebrew/bin:/opt/homebrew/Cellar/jenv/0.5.4/libexec/libexec:~/.nodenv/shims:/opt/homebrew/bin while sbt is running. As a result, if sbt internally invoke node, it is resolved as /opt/homebrew/bin/node, which is unexpected.
This bug affects sbt Scala.js projects using both nodenv and jenv, because sbt will launch node to run tests in these projects.
The text was updated successfully, but these errors were encountered:
Suppose you installed both
sbt
andnode
in Homebrew, say, under/opt/homebrew/bin
. When nodenv is initialized without jenv, the$PATH
would be~/.nodenv/shims/node:/opt/homebrew/bin
, thereforenode
is resolved as~/.nodenv/shims/node
, which is expected.Unfortunately, when jenv's sbt plugin is enabled, jenv will prepend the path containing
sbt
to$PATH
, which is/opt/homebrew/bin
, therefore the$PATH
becomes~/.jenv/versions/10.0/bin:/opt/homebrew/bin:/opt/homebrew/Cellar/jenv/0.5.4/libexec/libexec:~/.nodenv/shims:/opt/homebrew/bin
while sbt is running. As a result, ifsbt
internally invokenode
, it is resolved as/opt/homebrew/bin/node
, which is unexpected.This bug affects sbt Scala.js projects using both
nodenv
andjenv
, becausesbt
will launchnode
to run tests in these projects.The text was updated successfully, but these errors were encountered: