How to configure ALE w/ nvm or fnm?.. #4218
Unanswered
busticated
asked this question in
Q&A - Ask for help with problems
Replies: 2 comments 1 reply
-
hello did you find a solution? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Please try running the command ALE executes to see if that provides more information of the potential issue:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
hey there 👋
thanks for an awesome tool 🙏 ❤️
i'm running into weirdness trying to get ALE to work with my
nvm
managed node.js runtime. i'm actually usingfnm
but i'm pretty sure it's the same underlying issue. when i use thebrew
managed node.js, things work as expected.I see the command ALE is trying to run is:
...which results in:
however, when i run
/bin/zsh -c 'which node'
in my terminal manually, i see the expected path of/Users/me/Library/Caches/fnm_multishells/64376_1653599053758/bin/node
. likewise, when i run/bin/zsh -c 'node -v'
, i get backv12.22.12
which is correct.i came across this suggestion in a similar issue report but adding that (
set shellcmdflag=-lc
) to my.vimrc
didn't fix things. given the results running the default (/bin/zsh -c
), i wouldn't think i'd need to tweak my vim setup but 🤷♂️so, i'm stumped - any suggestions you could send my way would be very much appreciated 🙏 👍
My `ALEInfo` output
Beta Was this translation helpful? Give feedback.
All reactions