DEV Community

Discussion on: Debugging JavaScript, DOM, CSS and accessing the browser console without leaving Visual Studio Code

Collapse
 
pcjmfranken profile image
Peter Franken

I've been using this off and on for a few months now and I highly recommend everyone to check it out.

Not having to constantly switch between windows/spaces/virtual desktops is massive for keeping track of where you were wanting to do what. Perfect for my ADHD brain!

It's ridiculously easy to setup, I personally haven't experienced any crashes/bugs/slowdowns, and it's gratis. Go for it :)

Some things I'd love to see added down the line include automatic visual testing (opportunity to integrate with the upcoming VSCode native testing UI?), browser performance profiler, lighthouse integration, and displaying multiple screen sizes at once.

Collapse
 
codepo8 profile image
Christian Heilmann

Thank you, we're working on the multiple screen size idea. I haven't seen the native testing UI yet, and will investigate. We won't be implementing lighthouse, as it is a third party service, but we're working on integrating the issues panel data into the extension, much like the webhint extension does.

Collapse
 
pcjmfranken profile image
Peter Franken • Edited

That sounds great, looking forward to see those new features in action!

You and your colleagues have been killing it with Edge too. It's been ages since it last crashed (jinxed now of course 😉), amazing performance and low energy use on my MBP (getting scary close to Safari even!), the unique devtool features and these integrations are actually really useful, and as the cherry on top you finally got the sync feature working for 365 Business Standard tenant accounts :)

The only way I know how to access VSCode's native testing UI is through the Test Explorer UI extension which automatically installs microsoft/vscode-test-adapter-conv.... You then replace the extension's UI with the native one using the testExplorer.useNativeTesting setting.