microsoft / microsoft/vscode-edge-devtools
Instead of closing embedded Edge devtools on debug stop, return to previous Live Preview instance
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 827
- Forks
- 358
- Avg merge
- 20h 32m
- Merged PRs (30d)
- 10
Description
Is your feature request related to a problem? Please describe.
Hi!
I use Live Preview to start a local server and then open Edge devtools inside of VSCode without debugging and connect to localhost:3000 for seeing changes to the HTML, console and so on, it works pretty well. However when I want to debug something and launch the project the non-debug Edge devtools is completely replaced by the debugging version and so when I stop debugging the Edge devtools browser and devtools page disappear.
This is a bit annoying and I think it would be smoother if there was an option for just returning Edge devtools to the Live Preview/Live Server page.
Describe the solution you'd like:
When stopping the debug session Edge devtools should go back to its previous state (attached to a server) instead of completely closing. Closing Edge devtools makes more sense when it is launched in a separate Edge window which isn't really attached to VS Code except for the debugging.
Describe alternatives you've considered:
- Having debugging launch Edge in a separate window. For just debugging this kind of works but the Devtools stuff inside of VS Code is completely wasted since it is not connected to the debug session.
- Having debugging launch with "--headless" and clicking the inspect button in the debug icons to open Devtools code. This seems like it would work because it doesn't close when you stop debugging but the browser page also completely stops working after debugging stops.
Additional context:
Maybe I'm missing something but I'm just looking for a way to have:
- Edge devtools open when not debugging.
- Edge devtools switch to a debugging state when starting debugging.
- Edge devtools still open when stopping debugging.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Reproduce the Live Preview and debugging workflow in the VS Code Edge DevTools extension, then trace what happens when debugging stops and how the previous DevTools attachment is represented. Done means stopping debugging returns to the prior Live Preview or Live Server state without closing the embedded DevTools.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100