Dev Tools not refreshing Sources pointed to via map files.

2,074 views
Skip to first unread message

David Rankin

unread,
Jun 1, 2015, 12:09:17 PM6/1/15
to google-chrome-...@googlegroups.com
Since the latest install of Chrome (I now have 43.0.2357.81) the updates to source files pointed to by source maps are not updated in the Dev Tools when changed on the server and reloaded.

So if I visit a page with compiled js and open up Dev Tools Scripts I see the source files (eg ES6 or TypeScript) - great - but I then change the source file, recompile, and the new compiled javascript is loaded by Chrome but the Dev Tools doesn't update the source script. So breakpoints never marry up and the code original source that is shown is just wrong.

I have tried opening and closing Dev Tools, the tab and performing hard refreshes and still it shows the out-of-date source. I even have the Disable Cache flag ticked in Chrome Dev Tools.

I see the same issues in Canary.

Anyone got a fix or steps I can perform to wipe the dev tools sources cache?

Andrey Lushnikov

unread,
Jun 3, 2015, 5:25:22 AM6/3/15
to google-chrome-...@googlegroups.com
Could you try serving your sourcemaps with some additional headers to avoid their caching? E.g. 
Cache-Control: no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: 0

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/21e5926e-5e00-44a1-95e0-0e222f2a193f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages