I am working on a front-end project (JavaScript files) and the server adds a cache-busting value to the end of the URL, e.g., .js&bust=0.5647534393

My problem is I lose any breakpoints set in Chrome's Developer Tools after reloading. I do not have access to the server to disable it.

Is there any way to work around this constraint?

UPDATE: Adding debugger; to the JS source code is not a viable solution because I'm debugging production code.

I am working on a front-end project (JavaScript files) and the server adds a cache-busting value to the end of the URL, e.g., http://www.example./myfile.js&bust=0.5647534393

My problem is I lose any breakpoints set in Chrome's Developer Tools after reloading. I do not have access to the server to disable it.

Is there any way to work around this constraint?

UPDATE: Adding debugger; to the JS source code is not a viable solution because I'm debugging production code.

• javascript
• google-chrome-devtools

Share Improve this question Follow edited Mar 7, 2016 at 16:18 André Dion 21.8k77 gold badges5858 silver badges6060 bronze badges asked Mar 4, 2016 at 20:37 ArashsoftArashsoft 2,76766 gold badges3737 silver badges6161 bronze badges 10

• 3 i can't recall ever seeing anything like this, seems like a good point to bring up... – dandavis Commented Mar 4, 2016 at 20:38
• have you tried location.reload(true) in the console? may work (not sure, though) – Dominik Commented Mar 7, 2016 at 14:58
• @Dominik that seems like the opposite of what OP wants. – Evan Davis Commented Mar 7, 2016 at 14:59
• Any part of this discussion help you? stackoverflow./questions/8243742/… – James Hill Commented Mar 7, 2016 at 15:00
• 2 Why don't you "bust" it if it changes; aka, use a file timestamp or hash or mit number, as a parameter? :) – Caramiriel Commented Mar 7, 2016 at 16:07

 |  Show 5 more ments

2 Answers 2

Sorted by: Reset to default 6 +50

You can use a URL-rewrite Chrome plugin like Requestly (not free) or Redirector (free) and add redirect rule for your scripts.

Requestly for example lets you specify rules like:

I'm OFC assuming that if you strip the ?bust=xxxx part from the URL the server will still serve the correct script file. I tested it and it works like a charm in my local test environment - the breakpoints remain.

Hope it helps.

You can use debugger; within your code. If the developer console is open, execution will break. It works in firebug as well.