Chrome Firefox comes with debugging tools (detailed tutorial)

This article mainly introduces 9 techniques for debugging JavaScript using the built-in web debugging tools of Chrome and Firefox

We generally use the debugging tools that come with Chrome or Firefox to debug Javascript. This article lists several techniques. Techniques for debugging Javascript, mastering them will allow us to spend less time solving errors and bugs, thereby increasing development efficiency.

1. debugger

In addition to console.log, debugger is our favorite and fast debugging tool. After executing the code, Chrome will automatically stop while executing. You can even encapsulate it into a conditional and only run it when needed.

if (thisThing) { 
 debugger; 
}

2. Display objects in tables

Sometimes, there is a complex set of objects to view. You can view and scroll through console.log, or use console.table to expand it, making it easier to see what is being processed!

var animals = [ 
 { animal: 'Horse', name: 'Henry', age: 43 }, 
 { animal: 'Dog', name: 'Fred', age: 13 }, 
 { animal: 'Cat', name: 'Frodo', age: 18 } 
]; 
 
console.table(animals);

3. Use different screen sizes

It would be great to install different mobile device emulators on the desktop, but it is not feasible in reality. How to adjust the window size? Chrome provides everything you need. Jump to the console and click on the ‘Switch device mode’ button. Just observe the window changes!

4. Use console.time() and console.timeEnd() to test the loop

To know the status of certain codes Execution times are useful, especially when debugging slow loops. You can even set multiple timers by passing different parameters to the method. Let’s see how it runs:

console.time('Timer1'); 
 
var items = []; 
 
for(var i = 0; i < 100000; i++){ 
 items.push({index: i}); 
} 
 
console.timeEnd(&#39;Timer1&#39;);

The operation produces the following results:

5. Format the code before debugging JavaScript

Sometimes the code will have problems in the production environment, but your source maps are not deployed in the production environment. do not be afraid. Chrome can format your JavaScript files. The formatted code isn't as useful as the real code, but at least you can see what's going on. Just click the {} button in the source code viewer in the Chrome console.

6. Observe the calls and parameters of specific functions
In the Chrome console, you can observe specific functions. Each time this function is called, the parameters passed in will be printed out.

var func1 = function(x, y, z) { 
//.... 
};

Output:

This is a good way to see the parameters passed into the function. However, it would be better if the console prompts us for the number of formal parameters. In the above example, func1 expects 3 parameters, but only 2 parameters are passed in. If this parameter is not handled in the code, errors are likely to occur.

7. Quickly access elements in the console

A faster method than querySelector in the console is to use the dollar sign, $('css-selector') will return the first CSS selector Matches. $$('css-selector') will return all matches. If you use an element multiple times, you can save it as a variable.

8. Postman is great (but Firefox is faster)

Many developers use Postman to view ajax requests. Postman is really great. But it seems cumbersome to open a new window, write request objects, and then test them again.

Sometimes it's easier to use a browser.

When you use a browser to view, if you request a password verification page, there is no need to worry about the authentication cookie. See below how to edit and resend the request in Firefox.

Open the console and switch to the network tab. Right-click the desired request and select Edit and Resend. Now you can change whatever you want. Change the title and edit the parameters, then click Resend.

Below are two requests I initiated with different attributes:

9. Interrupting node changes

DOM is an interesting thing . Sometimes it changes and you don't know why. However, when you debug JavaScript, Chrome can pause when DOM elements change. You can even monitor its properties. In the Chrome console, right-click the element and select Break in settings:

The above is the text I compiled, I hope it is helpful to everyone

related articles:

How to implement a collapsible tree menu in Vue.js

How to use zTree tree menu

In How to implement table paging in vue element

The above is the detailed content of Chrome Firefox comes with debugging tools (detailed tutorial). For more information, please follow other related articles on the PHP Chinese website!