3 ms·
Even today the Firefox dev tools are quite far behind in my experience. For example, source maps are completely unsupported in the web console [0], so you get a
by Rezo 10y ago
Even today the Firefox dev tools are quite far behind in my experience. For example, source maps are completely unsupported in the web console [0], so you get a useless trace pointing to app.js:22312 while Chrome will tell you the target is actually indicator.js:21 right out of the box. That's a showstopper right there for any dev that's using Babel, Webpack, Browserify etc.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=670002 https://bugzilla.mozilla.org/show_bug.cgi?id=670002
- softawre 10y agoAgreed. Chrome even manages to work with 2 layers of source maps for my project (TS->JS->require). Not to mention that the FF "source file" view is this huge dropdown that is terrible to use when you have hundreds of files in various folders.
- nachtigall 10y ago> Not to mention that the FF "source file" view is this huge dropdown that is terrible to use when you have hundreds of files in various folders. They are working an another JS Debugger prototype with a different UI, see https://twitter.com/jlongster/status/737831071379783682 https://twitter.com/jlongster/status/737831071379783682 and https://github.com/jlongster/debugger.html https://github.com/jlongster/debugger.html