I'm becoming frustrated with Webstorm. It may be because I'm new to it and so far love it EXCEPT lately where it seems to cache code when I debug.
So here's what is frustrating me, just an example of steps to reproduce my frustration/issue:
1) I setup my debug config to point to http://localhost/whatever.html
2) Set debug points run in chrome
3) Hits my breakpoints fine
5) I notice there's this extra temporary file Webstorm is creating that's a copy of whatever code I'm testing. So for example during debug it creates this whatever.html file in webstorm when I am debugging
When I stop debug, that Http://localhost/whatever.html (which is the path I see if I mouse over this file webstorm is creating dynamically shows)
4) Stop the debug by pressing the stop (Square button) in the debug panel at the bottom of Webstorm
6) So I close out this temporary file or whatever it is that is apparently read-only and is a new tab in my Webstorm (new file during debug)
7) open back up my actual file (whatever.html or another js file, whatever) and make code changes
8) When I debug, for some reason it's debugging OLD code, the code before my changes. So in that http://localhost/whatever file it's creating it's creating a copy of it that does NOT include my latest code changes
9) end up having to completely close out Webstorm every time I make a code modification, close the browser, then re-run debug to be able to debug my LATEST code changes that I just made every freakin time
Lets look at this from a print screen perspective so you can see what's going on:
1) Start debug on an .html file
2) Run it, here you see it's running and the WS Chrome Plugin is connected and knows of this page
3) WS creates some kind of cached or temporary debug file during runtime within WS itself in addition to my actual file that's already open in WS; not sure why or what this is:
so what's happening? why is it creating this?
4) Ok so once I'm done debugging, figure hey I need to make more code changes to this .html file, I naturally stop debug, close the mysterious debugging .html cache file, close my browser (chrome) after removing cache manually just to make sure, and then make code changes and then restart debug
Now once it hits my debug point, it's not showing those new comments I had added, it's showing the code state before I had added those comments. What gives?
5) It starts back up in the browser and eventually hits my debug point again (the debug piont that lies in the mysterious .html runtime debug file that's created inside WS durign debugging)
only this time it's showing stale code even though I had changed the code! So what is going on?
6) Ultimately to be able to debug my new code changes I end up having to stop the debug process in WS via the stop button, close te mysterious debug html runtime file, close WS completely!, delete browser cache if it hasn't been, reopen WS and BTW, and having to stop the debug again! (see comments below) and then restart and debug...FINALLY I can debug new changes but this is ludacris.
Surely it must be something I do not know about how to work with WS?? lets hope. ( I have looked at your debug docs and as far as I've seen I can't find anything that talks about it creating this temporary debug runtime file within WS when debugging.)
and here's another weird thing to add for # 6
(when I reopen WS after this here's another strange thing, even though I had stopped the debugger prior to completely closing WS, when I reopen WS the debugger shows still running!)