Connor Peet

Interesting, do you mind grabbing a log of that case so I can see what the difference is?

The `program` should be the compiled JavaScript code, not Typescript. Things look alright otherwise.

Thanks for the kind words! Indeed, something we're talking about that would provide several things is the ability for language implementations in the editor to provide 'helper' APIs that debug...

I think that it only works because as a fallback we try to load the source from disk after appling path mappings (this is mostly used for Node.js) and when...

Actually, that should work. I thought it was in a different layer that the DAP server didn't have. https://github.com/microsoft/vscode-js-debug/blob/2bf84580011121e751e98bf648e28f50edafb3b5/src/targets/node/nodeLauncher.ts#L292 Not sure entirely what's going wrong without debugging it some more;...

Debug sessions use a different user data directory for Chrome than your default user profile. You can control the directory used via the `userDataDirectory` property in the launch.json.

Sorry, it's `userDataDir`, not `userDataDirectory`

This is generally the responsibility of the `outFiles` option; unlike browsers, Node.js (where I assume you're running) does not provide us a way to pause before a script with a...

Yea, executing the generated code in a subprocess should work. New debug sessions--each child process is a new session--will run a targeted re-scan of files (though if you run into...

Though the 'proper' way to do this is with a [prelaunch task](https://code.visualstudio.com/docs/editor/debugging#_launchjson-attributes) that builds your code before starting to debug it. As a slight benefit, the generation will run a...