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.
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.