Closed yoaquim closed 8 years ago
If that absolute path is correct, I can see no reason why this would fail occasionally but not always. If you start node
from the command line, and give it that path, does it work? Is there anything weird or non-deterministic about your file system (network mounts, etc)?
Not really. I installed this plugin by cloning via pathogen, and it's set up as a git submodule, since I back up my vim stuff to my own, personal repo. Running node [path]
doesn't return an error; I get "Listening in on port 60599".
+1 same here.
Ubuntu "node.js" command is "nodejs" not "node". It works by modify autolad/tern.vim line 15 from
let g:tern#command = ["node", expand('
I have same issue. Installed with Vundle
Solved problem with sudo npm install tern
I installed this plugin via Vundle, and did a local install via npm install
inside this plugin's directory (eg ~/.vim/bundle/tern_for_vim
). I can run the server standalone if I set with the NODE_PATH environment variable in the shell before opening vim to point it at ~/.vim/bundle/tern_for_vim/node_modules
. Need to look into this more for a better solution.
+1 same problem occurs on my mac also.
same problem here. Just need to go to ~/.vim/bundle/tern_for_vim
npm install
myself
+1 same issue
I used neobundle and installed tern via sudo npm and still the issue persists.
@twxia Was having this problem, but your solution fixed it. :tada: (although in my case the path was /.vim/plugged/tern_for_vim
).
(The fact that you have to npm install
in the bundle's directory is mentioned in the readme.)
😳 yeah it's is. And I realized that things broke because I did a reinstall of all my plugins without running the install script. Shame on me.
Close?
Let's.
Whenever I try and run a tern command, I get this:
Seldom will the server start correctly.
The module is there, I'm assuming, but maybe there's an issue when loading it?
Any workarounds/fixes to this?