Why does NiM need an active internet connection in order to operate?
ceremcem opened this issue · 6 comments
It turns out NiM doesn't work without an active internet connection because it tries to connect to http://chrome-devtools-frontend.june07.com/
.
Why does NiM need that while chrome://inspect/#devices
perfectly works without it?
More importantly, how can we configure NiM to work without an internet connection?
Try changing the DevTools URL under NiM options to the locally hosted version.
I assume when you mean no "internet connection is available" you are not including localhost network connectivity...
I've just confirmed that when you switch "Use Alternate DevTools." off and disabling my internet connection to the browser, NiM continues to work as it should. However if you're disabling the network in such a way that prevents any localhost traffic then it will affect NiM's ability to connect to the V8 inspector process which listens on localhost by default.
To be clear your DevTools version in NiM should look like one of the following to debug without Internet connectivity:
Basically NiM is going to need to communicate with the V8 debugger of your application.
To help more maybe you could provide more information about your dev environment as it relates to what I just wrote...
The image I sent is not delivered, here I'm putting it again:
The URL is not the same. How should I change it?
I assume when you mean no "internet connection is available" you are not including localhost network connectivity...
My localhost
connections work normally, I just switch of the internet, the WAN. Again, the chrome://inspect/#devices
works properly at those moments.
So I did discover a race condition which made the display of the actual configured DevTools Version inaccurate. It will take a bit before the change is reflected in the Edge/Chrome stores.
A fix in your case to display the actual version would be to toggle the "on/off" switch and refresh the options page. Once this fix is pushed, obviously this fix will not be needed.
As to the original issue, the problem is in fact that the DevTools Version was not configured to use the local version. And to change that, you should be able to simply toggle the setting.