Bringing the browser developer tools to Visual Studio Code

Re:Bringing the browser developer tools to Visual Studio Code by fishtoaster on Thursday October 01, 2020 @06:36PM (#24656898)

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.

[ Parent | on HN ]

Re:Bringing the browser developer tools to Visual Studio Code by robenkleene on Thursday October 01, 2020 @08:40PM (#24657668)

Interesting, thanks for pointing this out. This contradicts my comment here (https://news.ycombinator.com/item?id=24657613) a bit, but I’d be shocked if they didn’t get it working with Codespaces.

I do think it’s always going to require Edge though, I don’t see how Microsoft could resist getting tons of developers to install Edge for these features. I’m probably going to today. So a real VS Code strategy starts to emerge...

[ Parent | on HN ]

Re:Bringing the browser developer tools to Visual Studio Code by coldtea on Friday October 02, 2020 @03:16AM (#24659896)

>So a real VS Code strategy starts to emerge...

Sounds more like premature drama/conspiracy theory atm...

[ Parent | on HN ]

Re:Bringing the browser developer tools to Visual Studio Code by jameslk on Thursday October 01, 2020 @09:53PM (#24657995)

I don't think they need to embed a browser into VSCode considering it's already running in one (Electron). However I wouldn't be surprised to see a browser embedded into a browser these days either.

[ Parent | on HN ]

Re:Bringing the browser developer tools to Visual Studio Code by throwaway738 on Thursday October 01, 2020 @11:21PM (#24658475)

I'm pretty sure the electron browser engine moves slower than Blink.

If so, it would be extremely unhelpful for development and debugging since you would rarely have the latest engine on your machine, which would be the engine the majority of your customers would be on.

Using an external browser makes a lot of sense in that regards, and also, it separates the testing engine from the application itself, which allows for (although I doubt it's been implemented yet) testing in different browsers, or different versions of browsers, etc.

[ Parent | on HN ]

Re:Bringing the browser developer tools to Visual Studio Code by Shared404 on Friday October 02, 2020 @12:29PM (#24664266)

> I'm pretty sure the electron browser engine moves slower than Blink.

> If so, it would be extremely unhelpful for development and debugging since you would rarely have the latest engine on your machine, which would be the engine the majority of your customers would be on.

I would think that it would make sense to A) test in a slower browser anyways -- if your code runs well in a slow environment it'll run in a fast one as well, and B) Test in multiple browser engines anyways. Why would you only test one engine?

[ Parent | on HN ]

Re:Bringing the browser developer tools to Visual Studio Code by yunruse on Friday October 02, 2020 @03:11AM (#24659862)

It makes logical sense that MS would start with Edge, but I can see (for standards compliance) them expanding to work with other browsers too; it would be too great a selling point not to use.

[ Parent | on HN ]