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.
"Failed to load the ESLint library"
See original GitHub issueHi!
I have ESLint installed globally and .eslintrc.json in my home dir.
VSCode (Version 1.20.1) is installed with snap.
I use NVM.
which node
/home/ris/.nvm/versions/node/v9.6.1/bin/node
which npm
/home/ris/.nvm/versions/node/v9.6.1/bin/npm
which eslint
/home/ris/.nvm/versions/node/v9.6.1/bin/eslint
printenv NODE_PATH or ‘echo $NODE_PATH’ is empty BUT when I set "eslint.trace.server": "verbose" I got [Trace - 2:27:54 PM] NODE_PATH value is: /usr/local/lib/node_modules
I’ve already checked similar issues but can’t figure out the solution.
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
How do you start VS Code? Can you start it from the terminal where
npm config get prefixprints the correct value. Then everything is fine I guess. I suspect that when VS Code is started using some dock icon then the environment is not set correctly (e.g.the .bashrc usually doesn’t do all things when not in interactive mode). This is nothing VS Code not ESLint can fix. It is how shells / *nix behaves.You are right. It works when I start it from console. Thank you for your time!