Lets look at this from a print screen perspective so you can see what's going on:Ģ) Run it, here you see it's running and the WS Chrome Plugin is connected and knows of this pageģ) 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 in that file it's creating it's creating a copy of it that does NOT include my latest code changesĩ) 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 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)Ĥ) Stop the debug by pressing the stop (Square button) in the debug panel at the bottom of WebstormĦ) 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)ħ) open back up my actual file (whatever.html or another js file, whatever) and make code changesĨ) When I debug, for some reason it's debugging OLD code, the code before my changes. So for example during debug it creates this whatever.html file in webstorm when I am debugging So here's what is frustrating me, just an example of steps to reproduce my frustration/issue:ġ) I setup my debug config to point to 2) Set debug points run in chromeĥ) I notice there's this extra temporary file Webstorm is creating that's a copy of whatever code I'm testing. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |