Faster Smarter JavaScript Debugging in Firefox DevTools • Hacker News Board

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#71

Post by digitarald » Fri, May 17, 2019, 5:43 PM UTC

ptasker wrote: post #64

dlbucci wrote: post #18

You know, I've been using Firefox Dev Edition since it was Firefox Aurora (or Beta, I guess?), and it's great to hear that they are improving the dev tools! But I have to ask this in the nicest way possible: does anyone else think the tools just don't work a lot of the time? It's something I noticed especially when they switched to React. A few examples I frequently experience: 1) Stepping through TS frequently switc…

Yup, I also tried to use the debugging tools in the new FF Dev Edition with a larger React codebase and it's a bit buggy for sure.

Was this with 68? If so, could you share specific around what felt buggy.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#72

Post by vanilla_nut » Fri, May 17, 2019, 9:05 PM UTC

digitarald wrote: post #70

philliphaydon wrote: post #32

Earlier quoted context omitted.

I much prefer Firefox dev tools over chrome. The only time I use chrome is web socket stuff. Debugging css grids in Firefox (which I learned this year) is amazing.

fyi, we are picking up the websocket work this summer; so first parts might show up in 69, latest 70.

That's wonderful to hear! Websockets have definitely been a pain point for me trying to use FF dev tools in the past.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#73

Post by SahAssar » Sat, May 18, 2019, 7:38 AM UTC

grimgrin wrote: post #30

Logpoints are v cool I think https://developer.mozilla.org/en-US/docs/Tools/Debugger/Set_... Will certainly be something I use now and again

That's sorta possible already, just use a conditional breakpoint and end it with `return false;` and it will act the same.

Re: Faster Smarter JavaScript Debugging in Firefox DevTools

#74

Post by SahAssar » Sat, May 18, 2019, 7:41 AM UTC

_pdp_ wrote: post #57

That is cool but I am wonder why no browser provided any HTTP request/response interception response. In 2020 we still rely on proxies which is crazy given the amount of heavily lifting browsers do these days.

It'd probably be possible to build this using service-workers or an extension.