Error not showing up when node2 is not supported

[michelkaporin]

• VSCode Version: insiders
• OS Version: win10
• node: 7.5.0

Steps to Reproduce:

1. Have a simple javascript file, run vscode out of source and just add the node debug extensions
2. Node debug extension auto picks node2 however node2 does not seem to be bundled
3. I would expect an error message to be visible and not only shown in the console

ping @isidorn

[weinand]

When running out of source, OOTB no debugger is available.
Previously it was sufficient to just install node-debug.
But recently node-debug started to reach out for node-debug2 if it detects that 'node2' should be used.
-> when running out of source we now need to install both node-debug and node-debug2.

I've added the following dependency to node-debug:

	"extensionDependencies": [
		"ms-vscode.node-debug2"
	],

This results in a nice error alert trying to launch a node debug session.

However I noticed that when running out of source without any extensions installed (not even node-debug), then starting a launch config with type 'node' results in an error that is only shown on the console: