-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
volta + neovim compatibility issues #866
Comments
@stefanpenner which version of Volta are you using? Our recent 0.9.x releases should have (a) stopped discouraging use of |
@chriskrycho The changes in 0.9.x still didn't quite get this working. |
Ahhhh, that would do it; I misunderstood the dynamics with |
@stefanpenner - You have to specify node path in neovim config ( |
@mainendra that is a better workaround than the one I have listed, thank you. That being said it would be great to make this more seamless. In the meantime, I've changed my work-around to add the following to my if executable('volta')
let g:node_host_prog = trim(system("volta which neovim-node-host"))
endif |
I think we can convert this to enhancement story. |
Thanks for your solutions. For me they were not 100% clear, so if anyone had the same problem. It worked with me via this:
|
problem
neovim cannot discover node modules installed globally by volta
investigation
nvim +checkhealth
yields:
Given that when using volta,
npm i -g
andvolta global add
are discouraged, i run:volta install neovim
Which still has
nvim +checkhealth
yielding:Investigating further, neovim's algorithm essentially looks each of the following locations:
npm --loglevel silent root -g
yarn global dir
(for non unix)'$HOME/.config/yarn/global/'
(for unix)Likely ideal solution
Add volta support to neovim? corresponding neovim issue
Workaround:
The following has
volta
behave as if it wereyarn
, which appears to address the issue in question.yields a functional node.js provider for neovim.
The text was updated successfully, but these errors were encountered: