ChatGPT解决这个技术问题 Extra ChatGPT

How to force Chrome's script debugger to reload javascript?

I really like the ability to edit javascript in the chrome debugger however, I find that it can be really problematic getting the debugger to re-fetch the JavaScript from the server.

Sometimes I have to go as far just closing the debugger and reloading the frame works OK - but other times (an dI cannot pin down under what conditions this occurs) I have to clear my temporary internet cache. Sometimes I swear I have to close chrome completely, then clear the cache and then load the page before the debugger finally shows me the most up-to-date script.

(NB. There is no caching of the script by the web server)

I was wondering if anyone knew of a quick and easy way to tell the debugger to invalidate all its javascript and fetch it all anew on page reload?

Sometimes I even have to restart IIS Express to get things to reload properly.
I am having such trouble with this today that I've tried all the suggesstions here and filed a bug. I am totally dumbfounded at this point why I can no longer set breakpoints in my files. I can only set them in the page views and not the workspace views.

a
adrianbanks

While you are developing your script, try disabling the Chrome cache.

When you reload the page, the JavaScript should now get refreshed.

Chrome circa 2011

https://i.stack.imgur.com/0ovTz.png

Chrome circa 2018

https://i.stack.imgur.com/Do8Px.png

You can also access it on the network tab:

https://i.stack.imgur.com/kYWy6.png


So, does this apply all the time, or only when the debugger is open?
only when the Dev Tools are open
I've had that set all along, and now all of a sudden, I'm stuck with a certain file. Anyone find a solution?
This just added some years to my life. I tried the CMD+SHIFT+R but that didn't do it. Thanks
For those who are coming to this question more recently, note that the settings menu is off the three vertical dots menu in Developer Tools. There you will be able to check the box to disable cache.
S
Sebbas

https://i.stack.imgur.com/RtbdP.png

The context menu shown above is accessible by right clicking / presssing & holding the "reload" button, while Chrome Dev Tools is opened.

Empty cache and hard reload works best for me.

Another Advantage: This option keeps all other opened tabs and website data untouched. It only reloads and clears the current page.


That one is usefull especially because it is simple to explain. I was under the problem with a client not seeing the modification made on his website. Press F12, then right click on the reload button, choose Empty Cache and Hard Reload. I was done, thans to that comment :-)
Its's the best chrome feature :) , anytime mate.
Thanks! I was trying to figure out why the Reload button sometimes gave me a menu and sometimes didn't.
I had no problems with Ctrl+Shift+R when reloading Javascript files, but this would not bring back updated content that was served in HTML files. Empty Cache and Hard Reload did the trick for that.
Best way to do it, use this empty cache and hard reload
S
Steve Tauber

You can always clear a specific file by doing the following:

Open Dev Tools Click on the Sources tab Find your script / image / file Check the right panel to see if your file is up to date

If not:

Right click the resource in the left panel and choose 'Open Link in New Tab' Force a reload of the resource with the methods above. (See @Bishoy Hanna's example)

This is very handy if you have resources that are in frames and CTRL+F5 is not force refreshing them.


true. pressing CTRL + F5 = Clear cache refresh current page
I don't have a Resources tab.
@MikeW it's been renamed to Sources -- I've updated the answer
r
rink.attendant.6

Shift+F5 quickly clears the cache.


ctrl-f5 does not cut the mustard I am afraid. The old javascript file remains in the debugger.
T
Tony L.

Here's a shortcut to DevTools:

F12 to open Chrome DevTools F1 to open DevTools Settings Check Disable cache (while DevTools is open) as shown below:

https://i.stack.imgur.com/ixy8q.png

Note: Updated per Dimi's comment. They tend to move it so let me know or update the post if you notice that it's changed.


r
rink.attendant.6

For Google chrome it is not Ctrl+F5. It's Shift+F5 to clear the current cache! It works for me !


Why ? I don't understand what is the difference between that and a comment. At the end, the most usefull question will be see at the top of the post.
The questioner did not mention at any point Ctrl-F5, so by definition your answer is not an answer to the question asked by the questioner, its rather a comment, a correction to the other peoples answers and it should be treated as so.
V
Vijay Nandwana

On Windows, Ctrl+Shift+r would force reload the script in chrome.


S
Steve K

If you are making local changes to a javascript in the Developer Tools, you need to make sure that you turn OFF those changes before reloading the page.

In the Sources tab, with your script open, right-click in your script and click the "Local Modifications" option from the context menu. That brings up the list of scripts you've saved modifications to. If you see it in that window, Developer Tools will always keep your local copy rather than refreshing it from the server. Click the "revert" button, then refresh again, and you should get the fresh copy.


D
David Fahlander

It seems as the Chrome debugger loads source files into memory and wont let them go despite of browser cache updates, i.e. it has its own cache apart from the browser cache that is not in sync. At least, this is the case when working with source mapped files (I am debugging typescript sources). After successfully refreshing browser cache and validating that by browsing directly to the source file, you download the updated file, but as soon as you reopen the file in the debugger it will keep returning the old file no matter the version from the ordinary browser cache. Very anoying indeed.

I would consider this a bug in chrome. I use version Version 46.0.2490.71 m.

The only thing that helps, is restarting chrome (close down all chrome browsers).


M
Mohamad Chami

https://i.stack.imgur.com/BiLYU.png

Right click on reload button in chrome and click "Empty Cache and Hard Reload"


i
iamshravan

If the files which you are loading are cached and if the changes you have made does not reflect in the code then there are 2 ways you can deal with this

Clear the Cache as everyone told If u want Cache and only the files have to be reloaded , you can go to network tab of the dev tool and clear whatever was loaded. next time it will not load it from cache. you will have your latest changes.


M
Mister Verleg

There are also 2 (quick) workarounds:

Use incognito mode wile debugging, close the window and reopen it. Delete your browsing history


M
Mike W

Deactivating Breakpoints caused the new script to load for me.


s
scottbiker

In my opinion it's easiest to work in a 'private browsing session' of chrome, to ensure that your javascript files don't come from the cache.


a
antoine129

You can also use this Chrome extension to quickly switch between using or not the cache: https://chrome.google.com/webstore/detail/cache-killer/jpfbieopdmepaolggioebjmedmclkbap