Yesterday I finally took the time to work on one of those tasks that had previously never quite bubbled up to the top of my priority list. Since I’ve been working on Dasher 360 I’ve put up with using the developer tools built into Chrome for debugging. While these are pretty good – especially with source-map support, allowing us to debug the source TypeScript code – which is the main reason I haven’t taken the time to do otherwise, they do have their limitations: just for instance, you very often start to edit code in the debugger before realising you’re not modifying the source itself. This regularly drives me crazy.
So it was that I took the time to work out how to use a couple of VS Code’s debugging capabilities. Both my co-developer – Simon Breslav – and I have ended up gravitating towards VS Code as our primary IDE. He’s using it on Windows while I use it on a Mac, which is in itself pretty cool – as well as being a good test of whether what we’re…