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.
env: node: No such file or directory
See original GitHub issueI installed the plugin in a create-react-app-ts (https://github.com/wmonk/create-react-app-typescript) generated product; at first, nothing happened, there was a checkmark in the bottom row but the output was empty. Restarting VS Code and manuallly starting the Jest test runner (using the command runner) caused the error to appear in the output terminal.
I had NVM installed with a version set to the LTS version. Then I tried installing the latest version of Node via nvm, also setting as default. Then I installed the latest version of Node globally, using the installer, and restarting VS Code every time. All no luck.
Issue Analytics
- State:
- Created 6 years ago
- Comments:29 (3 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
If you have installed
nodeusingnvm, it won’t be in the place this extension expects it to be (/usr/bin/env).Workaround
You can make sure it is in the relative path by launching vscode in the root directory of your project:
If this is happening to you on a Mac, with iTerm and Zsh. I had to set the Explorer Kind (terminal application to use) in VSCode to external
Also, make sure this is not overridden at the Workspace level settings.