peoplemop.blogg.se

This should feel effortless, so we’ve scrutinized our own tools-and studied others-to give you the best possible experience. Debug all the things with new featuresįinding and pausing in just the right location can be key to understanding a bug. Second, continued investment in our performance and correctness tests ensures that the ever-changing JavaScript ecosystem, including a wide variety of frameworks and compiled languages, is well supported by our tools.

Guided by user feedback, we intend to use this time to improve new and existing features alike. Looking aheadįoremost, we must maintain a high standard of quality, which we’ll accomplish by explicitly setting aside time for polish in our planning.

We’ve also resolved countless bugs and polish issues. Thanks to our faster source-map support (and lots of additional work), previews are now displayed much more quickly when you hover your mouse over a variable while execution is paused. We fixed many long-standing bugs deep in the debugger architecture, solving some of the most common and frustrating issues related to lost breakpoints, pausing in the wrong script, or stepping through pretty-printed code. Predictable breakpoints, pausing, and stepping.No need to worry any longer about keeping the DevTools open! We found and removed many expensive calculations from running in the debugger when it’s in the background. Reduced overhead when debugger isn’t focused.js, regenerator) – benefiting the whole ecosystem.

Generating correct source maps can be challenging, so we also contributed patches to build tools (i.e. A revamped and faster source-map backend perfects the illusion that you’re debugging your code, not the compiled output from Babel, Webpack, TypeScript, vue.js, etc. We’ll share more of our performance adventures in a future post. This has resulted in a 30% speedup in our performance test suite. We’ve eliminated the worst performance cliffs that made the debugger slow to open. We can proudly say that all of those areas have improved in the past months: The debugger should be consistent, predictable, and capable of understanding common tools like webpack, Babel, and TypeScript. From initial loading and source mapping to breakpoints, console logging, and variable previews, everything needs to feel solid and responsive. A rock-solid debugging experienceįast and reliable debugging is the result of many smaller interactions. We invite you to open up Firefox Quantum: Developer Edition, try out the debugger on the examples below and your projects and let us know if you notice the difference. The work is ongoing, but Firefox 67 marks an important milestone, and we wanted to highlight some of the fantastic improvements and features. With these pain points in mind, the DevTools Debugger team – with help from our tireless developer community – landed countless updates to design a more productive debugging experience. Moreover, script debugging is a hard-to-learn skill that should work in similar fashion across browsers, but isn’t consistent because of feature and UI gaps. Above everything we heard the need for greater reliability and performance especially with modern web apps. We’ve been listening to feedback from our community. So the question for us, the Firefox DevTools team, has been, are the Firefox DevTools doing it right? Done right, it empowers developers to fix bugs quickly and efficiently. Script debugging is one of the most powerful and complex productivity features in the web developer toolbox.