Alert on launch

[wasinwill]

Issue Type: Bug

When opening VS Code Insiders since this morning's update, I'm getting this alert at every launch:

We did not find "node" on your path, so can not enable auto-attach in your environment
Source: JavaScript Debugger

The problem still occurs when all user-installed extensions are disabled.

VS Code version: Code - Insiders 1.50.0-insider (d1f2677, 2020-09-17T07:23:18.487Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item	Value
CPUs	Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz (4 x 3498)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: enabled_on protected_video_decode: unavailable_off rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	15.94GB (11.98GB free)
Process Argv	--crash-reporter-id 47798f4c-9d0b-4531-b0d9-c36278d01dbe
Screen Reader	no
VM	0%

Extensions (5)

Extension	Author (truncated)	Version
Bookmarks	ale	11.3.1
auto-close-tag	for	0.5.8
todo-tree	Gru	0.0.178
color-manager	roy	0.5.7
highlight-matching-tag	vin	0.9.9

[sweettyler]

same here on Linux.

Version: 1.50.0-insider
Commit: d1f2677
Date: 2020-09-17T07:03:46.695Z
Electron: 9.3.0
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux x64 3.10.0-693.17.1.el7.x86_64

Didn't have such an issue with the insider version released yesterday.

[agrimaldi74]

I clicked on the gear icon in the error message and followed the instructions to uninstall the JavaScript Debugger default extension and install the Nightly version, and the error is gone

[connor4312]

Thanks for the reports, this duplicates #106537

[sweettyler]

@connor4312 I am afraid this is not a duplicate of #106537. The reason is when I used the insider version of VScode "9e505675670d65138405321a60b0df4ddec28799" (which was built on yesterday) I didn't have this issue. If it's a duplicate I would have saw the error message much earlier or even 5 days ago.

So, the problem must be caused by changes between the insider version "d1f267742169584db010716d92addf50d4cd8139" and "9e505675670d65138405321a60b0df4ddec28799".

[sweettyler]

I just re-installed version "9e505675670d65138405321a60b0df4ddec28799" , and I have not this error message.

[connor4312]

Let's continue discussion in the linked issue. We can reopen this one if that issue ends up having a different root cause.