The experience of using Google Chrome’s local replacement of js and other files

The experience of using Google Chrome’s local replacement of js and other files

Recently, due to personal negligence, unexpected situations always occur on the website in the production environment. Therefore, it goes without saying that you need to debug the problem to deal with it and enable developer tool debugging.

After discovering the problem, how to verify the modified js file, avoid errors, and deal with it temporarily. This requires the overwrite file function in the developer tools. In fact, there are many tutorial posts on Baidu.

Write it down because I use it myself.

1. The top tab switches to the source code, and the left tree tab switches to the overlay file.

image.png

2. Click to select the local storage folder for overwriting, and then click Allow

image.png

3. Switch back to the page in the tree on the left, select the file to be replaced locally, right-click to save and overwrite.

image.png

4. Edit and save directly on the developer tools, or paste the local modified file, paste and save. Of course, this is a js file. For other media files, you need to go to the folder in step 2, find the corresponding file and replace it. Finally, refresh the page and the local replacement will take effect.

Guess you like

Origin blog.csdn.net/qq_36644198/article/details/131723549
Recommended