When I was part of F12 team, we had proposed this to head is developer tools but he was a bit dismissive at the time. Edge was the future. Chrome was the enemy.<p>Oh how times have turned. IIUC, this is chrome devtools packaged as a vscode extension using chrome remote protocol to talk with the browser.<p>I’m glad this finally landed.
Looks like this requires Edge to be installed on whatever machine you have VS Code installed on. I was kinda hoping that this was a browser properly embedded into VS Code so I could use it in github's Codespaces. No such luck, I'm afraid - trying to install the extension throws an error.
I wrote a piece that got some discussion here on VS Code (<a href="https://blog.robenkleene.com/2020/09/21/the-era-of-visual-studio-code/" rel="nofollow">https://blog.robenkleene.com/2020/09/21/the-era-of-visual-st...</a>). After writing that piece and reflecting, I decided that VS Code did in fact have one weakness: It doesn't have an embedded browser. I even tried to start a conversation about it on the VS Code Dev Slack here's what I said:<p>> Any thoughts in integrating a browser into VS Code? Panic's just released text editor for macOS, Nova, has this feature. The obvious thing it gets you is a live updating preview of HTML files, but taking it further: With VS Code's development community, this seems like it could be the path forward for features like being able to instantly jump to editing the source file for a CSS rule or an HTML element from the DevTools, or jumping to a component's source file from the React DevTools. I'm aware there a couple of projects that have tried to do integrate a browser into VS Code, but nothing has really come to fruition yet, any thoughts?<p>(Didn’t get much of a response, but obviously no one would talk about this if they knew.)<p>The above summarizes my thoughts, but here’s another one: This is a key component of GitHub Codespaces. One of the weaknesses in remote development is the round trip between the developer server process and the browser is less seamless than when doing local development. The IDE-style debugger integration doesn’t work without running Chrome on the same machine for example.<p>Anyway, VS Code now doesn’t have any weaknesses that I’m aware of anymore.
I've come close to setting up <a href="https://github.com/skeeto/skewer-mode" rel="nofollow">https://github.com/skeeto/skewer-mode</a> several times. Things like this always demo better than they actually improve my productivity, though. Especially with modern frameworks that don't let you redefine everything. (Odd that common lisp is still head and shoulders above most languages with how much you can redefine at runtime.)
FYI you have to enable the network tab in the extension settings for it to show up, it is not enabled by default.<p>They kind of mention this in the article but it wasn't super clear.
I wonder how this would help with WebView. I develop an extension that loads the page inside the WebView, but having to use the WebView's inspector sucks. If this new tool can let other extension use it's panels, it would be awesome.