Allow to pick exact tab to attach to if several tabs match urlFilter

During my work I usually have several pages that will match urlFilter e.g. *example.com/app*:

http://client.staging.example.com/app/orders/order1
http://client.local.example.com/app/orders/order1
http://client.local.example.com/app/orders/order2
http://search.local.example.com/app/results

So I can compare behaviors/outputs/request between them and having only one tab open is not an option.

At this point when I run debug config with "type": "pwa-msedge", "request": "attach", it will attach to “random” tab that matches urlFilter.

Current Edge/Chrome debugger extensions provide ability to pick exact tab before attaching to it. Edge example

Would be great to have similar approach using built-in extension.

I was thinking that #437 will allow this, but apparently it does something else.

---

Version: 1.46.0-insider (user setup) Commit: 6849775440496504e0677ffcf2a46d47ad9130f5 Date: 2020-05-15T05:30:56.857Z OS: Windows_NT x64 10.0.18363

JavaScript Debugger (Nightly) Built-in v2020.5.417

[connor4312]

Sounds good. One way to diagnose path issues is adding a debugger; statement to your code, and then when it’s hit you can see the path of the readonly file that gets opened – that’s the path that js-debug thinks your source should be at.

[IllusionMH]

I’ve introduced some logic to preserve the original source paths and map between them.

Thanks I was able to have "webpack:///../*": "${webRoot}/*" for simple repro case 👍, but doesn’t work for main large project.

Will try investigate further and create new issue with details.