For me, on both my personal and work machines, this error (or at least a very similar one) occurred because of the "JavaScript Debugger (Nightly)" VSCode extension.

Some jiggery-pokery between disabling / enabling / re-installing that extension removed the error.