A compatibility wrapper around the BrightScript debug protocol https://developer.roku.com/en-ca/docs/developer-program/debugging/socket-based-debugger.md
Currently the debugger always assumes the file found at the end of the source-map chain is valid. That's what gets sent to vscode. However, if that file doesn't exist, then we lose the ability to debug the current line. Instead, we should check for the existence of the sourcemap-resolved file, and if missing, send the debug location. That way we at least fall back to stepping through the file from the staging folder.
Currently the debugger always assumes the file found at the end of the source-map chain is valid. That's what gets sent to vscode. However, if that file doesn't exist, then we lose the ability to debug the current line. Instead, we should check for the existence of the sourcemap-resolved file, and if missing, send the debug location. That way we at least fall back to stepping through the file from the staging folder.