I published a piece yesterday suggesting Visual Studio Code might be the most popular text editor for a long time, possibly for decades to come. Love to hear thoughts from anyone here. https://blog.robenkleene.com/2020/09/21/the-era-of-visual-studio-code/
Maybe I'm mis-understanding what you're looking for. Here's HTML live preview in VSCode
I agree with you the Chrome DevTools are better than the VSC Debugger. I don't know what if any features of the Chrome DevTools can't be written via chrome extensions (since there are extensions that add features to the devtools)
AFAIK most of the DevTools are written in JavaScript using the extension API so it might be possible for VSCode to apply them to an HTML page, though I suspect rather than copy the tools they should just let the HTML plugin expose the existing devtools for its preview.
You might also argue that trying to stuff too many things into one place might make it jack of all trades master of none. It might be better to talk to the Chrome team and see if they can come up with an API to tell you embed your editor of choice in the devtools? I don't know. At some point it feels like the 2 things are going to conflict with each other. VSC is a code editor, not a JavaScript editor, so I'd prefer it not hard code a JavaScript debugger and then in turn need a C++ debugger, C# debugger, a Swift debugger, a Rust debugger, etc... At the same time, of course I want better tools period.
A few maybe relevant links.
You can run the devtools on the devtools (debug the debugger)
https://docs.google.com/document/d/1WNF-KqRSzPLUUfZqQG5AFeU_Ll8TfWYcJasa_XGf7ro/edit#
Only pointing that out just to show that the devtools are written in JavaScript so if you feel like contributing you can either copy them into an vscode plugin, or add/propose changes to chrome to help get the solution you're looking for.
I think the confusion was just because I mentioned live browser for previewing HTML, but that’s just one use case. The real goal is of course better dev tool integration when making entire web apps.
I’m not sure the line between JavaScript editor and code editor matters much. VS Code is Chromium, the dev tools are already bundled in to it. And of course any special dev tools could (and probably should) be extensions, just like everything else. The VS Code app just doesn’t expose things like Chromium web views and the dev tools to extension developers, if they did, I’m guessing this work would already be well underway.
The assumption I’m challenging is whether the dev tools should be part of the IDE or the browser (I don’t see the benefit of VS Code in Chrome, I want my dev tools next to the source code). I think they’d be more useful as part of the IDE (via extensions), because they’d have more seamless interaction with the source files. This is how Xcode (the other dev environment I know well) works, and I’d imagine most IDEs for non-web programming language. The whole browser dev tools concept seems to be a historical artifact of there not having been a better place to put these tools before, but with VS Code where it is today is argue that’s a better place now.
(Running a web server process in the terminal is another similar historical artifact. VS Code has a decent solution to this with launch.json
files.)
Regarding “I don't know what if any features of the Chrome DevTools can't be written via chrome extensions (since there are extensions that add features to the devtools)”. The idea is to be able to jump to the relevant files in your editor from the dev tools, like easily edit the source HTML for a tag. You can do this today with Workspaces but it’s so many steps to setup because the dev tools are so far from the IDE that it’s not worth it to use. It’s UX problems being solved here, not what’s technically possible.
We’ll there goes VS Code's last weakness... https://blogs.windows.com/msedgedev/2020/10/01/microsoft-edge-tools-vscode/