What is set by mise link
is not observed when running mise use
or mise doctor
#3539
Replies: 7 comments
-
seems to be working fine for me:
|
Beta Was this translation helpful? Give feedback.
-
It never works for me.... after running but if I run
this is very very strange as I already have installed all required node versions via
Clearly mise doesn't detect the linked node version:
I wonder "where" does this node installation information come from for mise, if there's any state being maintained. |
Beta Was this translation helpful? Give feedback.
-
you need to set it to the directory containing the full node tarball, not the |
Beta Was this translation helpful? Give feedback.
-
You think I didn't try all different directories already? I spent a few hours on this (even tried to look at the code) and couldn't find the solution yet.
|
Beta Was this translation helpful? Give feedback.
-
I'm not sure, that looks correct to me. Perhaps the e2e test might elucidate why this isn't working for you. |
Beta Was this translation helpful? Give feedback.
-
here's this for what it's worth:
|
Beta Was this translation helpful? Give feedback.
-
Describe the bug
I'm running on M3 MacBook and I have an issue with installing [email protected] via
mise install
.So I've used installing it by
nvm
which worked fine.And then I ran
mise link [email protected] <node binary path returned by nvm which>
.and
mise ls
command shows it correctly:But I tried to use it by
mise use [email protected]
then it removes the symlink and tries to reinstall the node version.Also,
mise doctor
command shows it's still missing even if it's linked.Because I can't run
mise use
command, switching node version via nvm in another place affects the version of node in this repo.To Reproduce
Expected behavior
mise doctor
andmise use
should observe what's set up bymise link
.mise doctor
outputAdditional context
N/A
Beta Was this translation helpful? Give feedback.
All reactions