vscode: VSCode-Insiders 2020-09-17 update produces error on startup: "We did not find "node" on your path, so can not enable auto-attach in your environment"
Version: 1.50.0-insider (user setup) Commit: 3156f1fbfcbb7bdd5f7aa24b4cde71526d1980c8 Date: 2020-09-17T17:22:44.035Z Electron: 9.3.0 Chrome: 83.0.4103.122 Node.js: 12.14.1 V8: 8.3.110.13-electron.0 OS: Windows_NT x64 10.0.19042
Steps to Reproduce:
- Start VSCode-Insiders
- Observe error popup.
Does this issue occur when all extensions are disabled?: Yes
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 2
- Comments: 21 (16 by maintainers)
@pmsjt I think there is > 99% chance this is a bug:
This doesn’t happen when running the insider version built on 09/16 and it happens when running the version built on 09/17. So it’s changes made within these 24 hours that causes the error.
This error will gone if you install the nightly version of JavaScript Debugger (ref https://github.com/microsoft/vscode/issues/106938).
if it is caused by what is described in microsoft/vscode-js-debug#708, I should have seen this error much earlier, instead of just today.
Other than a bug, there is not a logical explanation.
Fair point, I removed the flag 🙂
Well, the bug has “as designed” flag set, and we’ve established that is incorrect. Can we have that removed?
The problem with closing an issue before it is validated is that it may lead to people opening more and more issues if they are experiencing a problem and the only existing report of that is closed.
Is this closed on purpose? It would be nice for us to verify it, first.