SLKnutson
SLKnutson
The explicit types are technically correct, but as far as I am aware, not useful for the consumers of jest-extended. There may be use cases that I'm not familiar with....
It would be nice to have this fixed. Relying on returning the correct http headers is painful when hosting a static app.
@bradzacher What is the purpose of the "ignore" parameter then?
When I remove the `.send('Network.enable')` command from NetworkManager, I no longer have this issue. Sending `'Network.disable'` afterwords also works, but I don't know of any way to get the CDPSession...
I'm using `Network.disable` proactively, calling it once right after I open the page. It looks like that clears out any existing request data and stops any more from being held...
I don't think this is something you can debug with the memory usage inspector because the leak occurs in the chrome process itself, not javascript.
As I understand it, this isn't just about the warning. The warning is telling the developer that the code isn't working the way they intended. In our case, we rearranged...