-
Notifications
You must be signed in to change notification settings - Fork 231
Network tab #12
Comments
A question for @makslevental and others who've hearted, are you primarily interested in incoming network requests i.e. inspecting server routes, or outgoing network requests made by node? |
@patrickhulce I would say both? A node server is a good use case where you want to see incoming requests to your server and outgoing requests made by the app/backend. Points for being able to filter between incoming/outgoing requests. |
Literally first thing I looked for after seeing the post on HN. @patrickhulce Both if possible, it’d be a complete life saver to see the requests as they fly in and out, rather than debugging just the payload before/after flight, or proxying the requests through another app. |
Yeah makes sense I've just been thinking lately that it'll require a completely new UX. I'd love to see incoming routes with a breakdown of time spent in each middleware, incoming request, final response body, etc. I could see the existing network panel being extremely confusing if outgoing and incoming were intermingled (it's already bad enough when you're trying to look at a service worker page 😆) |
If it's easier to just add in outgoing requests that would be really helpful. |
We are working on this feature request. Stay tuned. |
@ak239 I'm interested in this feature, is there a way I can help? |
This would be a fantastic feature! |
any workarounds for getting this will be amazing |
I'm thrilled to announce that I'm working on WIP PR for this #282 |
想知道进度。。。 |
https://news.ycombinator.com/item?id=17581719
this is a thing i've always wanted that i've never known i've wanted until now. seems like it should be possible given that this is dev tools ripped out of chrome but of course i'm not sure given how massively complex this project is. just wondering.
thanks for the work!
The text was updated successfully, but these errors were encountered: