Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Local tern installation instead of global one

See original GitHub issue

I switch node/npm versions in different projects and having to install globally means that I have to install it on every version that I use, which is kind of a pain. So if we can make this a local dependency for the plugin like tern_for_vim this would be great.

Issue Analytics

State:
Created 7 years ago
Comments:14 (11 by maintainers)

Top GitHub Comments

1reaction

FuzzOli87commented, Apr 21, 2016

@carlitux While gulp-cli, ava-cli, babe-cli etc… should be installed globally. Like @ahmedelgabri I install all of that as a devDependency and either run them through npm scripts and I also have export PATH=$PATH:./node_modules/.bin in my .zshrc file. This keeps my global installs relatively clean.

I do this because I work on multiple projects that tend to have different tools. One might use Grunt, the other Gulp or the worst case recently was the different versions of Babel.

I do have tern_for_vim installed as well. I thought it was compatible, but it doesn’t look like it.

1reaction

jacobraskcommented, Apr 20, 2016

Using $(npm bin)/tern as the tern binary is the best choice in my opinion.