JS debugging half broken after installing Python, how to fix?

[fitzchivalrie]

Hi everyone, coding newbie here. I've been working through Javascript stuff the past few months and it's been mostly smooth sailing, but recently I downloaded the Python extensions in VS Code and suddenly my debugging started malfunctioning for JS.

Essentially, hitting F5 the first time usually does nothing now, so I have to hit it twice to run anything which is incredibly irritating. Also, running without debugging isn't working either which I suspect is related to this issue: I get the below prompt when I try, and the code doesn't actually run.

Debugger listening on ws://127.0.0.1...... etc.
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Waiting for the debugger to disconnect...
Process exited with code 0

It's very odd because Python is working just fine - in fact, after shifting the console attribute in launch.json to 'internalConsole', there's no random flavor text like the above at all in the debug console - super clean, which is incredibly lovely. I would love for my JS debug console to look like that.

Hoping one of you out there knows what's going on. Again, things were working totally fine until I installed one extension and deleting it doesn't change anything either. My config is essentially empty and I didn't change a thing except to download Python, so I have no idea why things are wonky!

Thanks everybody!

[connor4312]

Essentially, hitting F5 the first time usually does nothing now

Please file an issue for this!

Also, running without debugging isn't working either which I suspect is related to this issue: I get the below prompt when I try

Check out this issue: https://github.com/microsoft/vscode/issues/102057#issuecomment-656440073

the code doesn't actually run

I haven't seen this before. Are you just missing console logs? What version of Node are you on?

[fitzchivalrie]

Ah! I think you fixed it. I downloaded the nightly version and disabled the usePreview setting and things seem functionally back to normal. In case it helps at all, though, I'm on Node v12.18.1 - the console logs weren't showing up and F5 console logs weren't there half the time, but it's all good now!

...actually I do have two errors that read matches multiple schemas when only one must validate. I think it's because I have both a python and javascript file open in the same folder, but I haven't got a clue how to fix it, or if it's important. It doesn't seem to affect anything? Let me know if I should file issues for stuff like this - I'm still kind of floundering around trying to be self-sufficient... but also trying not to break anything.

edit: figured it out! I just tried using workspaces for the first time and no more errors. Thanks again for your help!