How to find the key points in the complex debugging process of JavaScript

This article is about how JavaScript looks for key points in the complex debugging process. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

Look for key points in the complex debugging process

In more complex debugging, we sometimes want to output many lines. All you can do is maintain a good output structure and use more console functions, such as console.log, console.debug, console.warn, console.info, console.error, and so on. You can then browse quickly in the console. But sometimes, some JavaScrip debugging information is not what you need. Now you can beautify the debugging information yourself. When debugging JavaScript, you can use CSS and customize the console information:

Console.todo = function (msg) {console.log ('% c% s% s% swords, 'color: yellow; background-color: black;',' -', msg,'-');} console.important = function (msg) {console.log ('% c% s% slots, 'color: brown; font-weight: bold; text-decoration: underline;',' -', msg,'-') } console.todo ("This is something that' s need to be fixed"); console.important ('This is an important message')

Output:

For example:

In console.log (), you can set strings with% s, set numbers with% I, set custom styles with% c, and so on, and there are many better ways to use console.log (). If you are using a single-page application framework, you can create one style for view messages and another for models, collections, controllers, and so on. Maybe you can use your imagination like wlog,clog and mlog!

Thank you for reading! This is the end of this article on "how to find the key points in the complex debugging process of JavaScript". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!