feat: use devtools api to get response payload #1019
Conversation
| chrome.devtools.network.onRequestFinished.addListener(handleNetworkRequest); | ||
|
|
There was a problem hiding this comment.
onRequestFinished implies the full response has been returned right? The extension needs to be able to support HTTP streaming, so that you can later rewind time to see when specific chunks come in.
Do you know of a way to do that without using a fetch patch?
There was a problem hiding this comment.
Yes that is correct. You get access to the request and response. I was not aware of the timing feature for individual chunks within the same response. I guess that that is not possible with the API offered by the devtools. I will dig a little deeper to find a definitive answer for it.
If it turns out that it is not possible, you can close the PR.
There was a problem hiding this comment.
You'd be able to see the future in action if you have a suspense boundary on a page with an artificially slowed down component inside. The response is a HTTP stream, and it won't wait for the slowed down component to finish to begin sending.
I will dig a little deeper to find a definitive answer for it.
Thanks, let me know what you find!
This PR uses the chrome devtools api to access the response palyload instead of patching fetch
There is an issue that I could not resolve (i suppose it is an issue of the chrome devtools), that sometimes during nextjs development mode the payload of the response can not be accessed.