I have recently run into an issue using vscode-js-debug with nvim-dap in Neovim, Powershell and Windows.

I opened a bug report with nvim-dap, but I was wondering if lack of path normalization in the adapter could be at fault.

Long story short: I was having problems with unbound breakpoints when debugging an Angular application, which was working fine before. I was able to narrow down the problem: when nvim-dap sends the path field for the source object in a setBreakpoint request, it uses the absolute path with forward slashes; VSCode, on the other hand, sends the exact same path, but with backslashes. It works in VSCode, but the forward slash in nvim-dap makes the breakpoint unbound.

I was wondering if this path normalization could be done at the adapter level, insteaf of creating another conditional case for nvim-dap.