3 ms·
Same here, but for Firefox (which I prefer for WebDev). Just switched to VSCode because it's the only editor[1] that has a working JS Debugger for it: https://g
by nachtigall 10y ago
Same here, but for Firefox (which I prefer for WebDev). Just switched to VSCode because it's the only editor[1] that has a working JS Debugger for it:
https://github.com/hbenl/vscode-firefox-debug https://github.com/hbenl/vscode-firefox-debug
[1] Though other editors might follow. Just saw that the Firefox Debugger team would be interested in integrating their new react/redux based debugger into Atom: https://twitter.com/clarkbw/status/783358566858010624 https://twitter.com/clarkbw/status/783358566858010624
- fandango 10y agoWould you say the Firefox debugger works equally well as the Chrome variant? (In terms of responsiveness, integration, overal experience). I really fancy the JS debugger of VSCode but I'd hate to drop Firefox for that.
- nachtigall 10y agoI don't understand your question. > Would you say the Firefox debugger works equally well as the Chrome variant? Are you talking about the native debugger. Not sure. I only use the Chrome debugger from time to time, but mostly use the Firefox debugger. So it's ok, but since I use it all the time, I know it has its warts... Anyway, there are completely rebuilding it using react.js at the moment: https://hacks.mozilla.org/2016/09/introducing-debugger-html/ https://hacks.mozilla.org/2016/09/introducing-debugger-html/ > (In terms of responsiveness, integration, overal experience). As said I use it (firefox and vs code) all the time as a JS developer. > I really fancy the JS debugger of VSCode but I'd hate to drop Firefox for that. That's the part I really do not understand. I do use Firefox (and its native devtools), and I do use VSCode plus its Firefox extension. So no reason to drop Firefox ;)