4 ms·

debugging is the best I've ever experienced. Webstorm debugging was problematic for me a year and a half ago. Visual Code has surpassed Atom by far as well, whi

debugging is the best I've ever experienced. Webstorm debugging was problematic for me a year and a half ago. Visual Code has surpassed Atom by far as well, which weirdly does NOT support client side debugging for javascript (and that's a major mistake on Atom's behalf). In VSCode debugging is of course provided by 3rd party packages, but their API and rich debugging GUI seems to make it extremely easy to hook into it. In short, if you're using webpack-generated sourcemaps, VSCode is the way to go. Being able to finally debug in your actual code (rather than Chrome devtools) is a dream come true! Otherwise I love their built-in linting and git support. Here's the chrome debugger: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome https://marketplace.visualstudio.com/items?itemName=msjsdiag... I've submitted several bug reports to its creator (a developer at Microsoft) and received prompt response as well as fixes! It lets you attach to running browser windows or launch a new one. Next and perhaps more importantly, there's a debugger for React Native!: https://marketplace.visualstudio.com/items?itemName=vsmobile.vscode-react-native https://marketplace.visualstudio.com/items?itemName=vsmobile... And it works flawlessly, and brings along IntelliSense for React Native elements/apis, etc. If you're a javascript developer, drop what you're doing / what you're using, and make the shift to VSCode. If you're using Atom currently, you can likely find your same themes in the VSCode extension directory, which--for me--made the shift almost seamless (the feel shares a lot in common with Atom because of its Electron roots).

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 ago
  Would 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 ago
    I 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 ;)

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 ago
Would 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 ago
  I 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 ;)