Two essential tools for Javascript development

Reprinted please indicate the source: http://blog.csdn.net/horkychen

Some colleagues have encountered the problem of debugging compressed JavaScript code. today, Charles is finally found on stack overflow, and the map local function is used. although the principle is simple, it is a Web Proxy. When reading a webpage resource, replace the original file with a local file. It is indeed a function that can solve the actual problem. especially for compressed JS scripts, it is not easy to set breakpoints or add some logs. At this time, Charles can help us solve this problem. since all files are located in the local file, we can do whatever we want.
Other modifications such as CSS are okay. (The debugging tool provided by the browser can support fine print to solve a part of JS scripts that are crowded together ).

In addition to Charles, there is a similar software Fiddler. Below is a simple comparison:

Charles (Mac OS) Business Edition www.charlesproxy.com/download/

Fiddler (Windows only) Open-source www.fiddler2.com

* There are already a lot of related information. I will spread it again. Or that sentence: to do good deeds, you must first sharpen your tools!

The software functions are not complex and easy to understand. I have posted two pictures of Charles here. For more information about Fiddler, see the article contributed by the Alibaba team: Using Fiddler to improve front-end efficiency
(Instance ).

Then you can specify a local replacement file.

You can directly use the browser's debugger to see the effect.