Launching Node app through WebStorm debugger seems to be caching proxies I've changed
I needed to change some proxies I was using -- in particular I deleted them both from .zshrc and .npmrc. I also made some proxy changes to the Mac (10.14) Network config, but the proxy remained there. Subsequently I could not get a Node (12.13.0) app launched through the WS debugger config to work. It took me the longest time to figure out that when launched through the debugger the app was somehow still trying to go through the proxies. When launched from iTerm or from WebStorm's own terminal, the app worked fine.
I did 'file->invalidate caches', and I made a new debug config, and in the end restarted WebStorm entirely, but the situation remained the same.
Where might the debugger be loading this proxy from? Is there some '.rc' file that it uses? Has it cached it somehow? How can I proceed, and in the future, what should I do to avoid this situation?
Thanks for any help --
Please sign in to leave a comment.
Please try starting WebStorm from terminal ( using
open -a /Applications/WebStorm.app)- does the problem persist?It seems to have resolved itself 'automagically' : this morning I rebooted the machine and restarted WebStorm and it seems to work OK. The machine is a laptop and was moved to a different location over the weekend -- I don't know if that has anything to do with it.
In case this happens again: does WebStorm or the debug configuration cache information like proxies in any file/location that I could try deleting?
No, it doesn't