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.
node version does not match that in terminal
See original GitHub issueOutput tab says:
[Info - 2:18:01 PM] ESLint server is starting
[Info - 2:18:02 PM] ESLint server running in node v14.16.0
[Info - 2:18:02 PM] ESLint server is running.
Whereas terminal says:
14:18:04 ➜ node -v
v16.11.1
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:16 (6 by maintainers)
Top Results From Across the Web
"node" version "14" doesn't match your global version "12 ...
Most likely you have a problem with Firbase-tools. When installing Firbase-tools via the binary, it is installed with version 12 of Node.
Read more >Gatsby 5 Upgrade. Say No to YOLO
In this post Paul explains how he upgraded paulie.dev to Gatsby 5 and is now experiencing ~47% faster build times!
Read more >Install npm in a Few Easy Steps | CSS-Tricks
Download the latest version of NVM for Windows. · Open the terminal and run the nvm list available command to see a list...
Read more >Introducing Volta - it manages your Node.js versions so you ...
Introducing Volta - it manages your Node.js versions so you don't have to. Web development is tough enough as it is, something as...
Read more >IntelliJ Terminal not working - NodeJs Version
Please update your Node.js version or visit https://nodejs.org/ for additional instructions. I am a mac user. macOS Big Sur. How can I ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@gajus by default the extension uses the node runtime shipped with VS Code. This is why you see
v14.16.0.The way how to use a different node runtime is the
eslint.runtimeproperty. Usually usingnodeas a value should pick the default version even if you are using a node version manager.An example snippet to add to vscode settings would be ideal here.