[Next14 app dir] Debugging network requests outcomming from server components
Unanswered
Saltwater Crocodile posted this in #help-forum
Original message was deleted.
12 Replies
Cuban Crocodile
Bump this would be good, I know of node inspect, but that only works on development not production
Japanese Spitz
https://github.com/oslabs-beta/NextInspect
This looks like the thing that you're looking for. I haven't tried it yet, but by reading the repo, it looks to work for ssr and csr pages.
This looks like the thing that you're looking for. I haven't tried it yet, but by reading the repo, it looks to work for ssr and csr pages.
Cuban Crocodile
Kind of annoying that you would have to install something extra just to debug a next application. Of course I will use it though, but nonetheless should up to the framework to provide a way to do it natively
Cuban Crocodile
I've tested this tool, but it does not show the request that are being made in the server, it only shows you the whteher a component is client or sever component as well as calls being done in the client side of things ...
American Crow
I use a combination of
and https://console-ninja.com/
not the greatest solution but def. helps me
module.exports = {
logging: {
fetches: {
fullUrl: true,
},
},
}and https://console-ninja.com/
not the greatest solution but def. helps me
@American Crow I use a combination of
js
module.exports = {
logging: {
fetches: {
fullUrl: true,
},
},
}
and https://console-ninja.com/
not the greatest solution but def. helps me
Cuban Crocodile
but again the issue is that this will work on development, but will not work on production ready, imagine this if a team of 5 devs and then you have support team, the support team in the past would be able to see the network tab, but now that is gone, they would have to understand the code and not really fast to reproduce of debug
@Cuban Crocodile but again the issue is that this will work on development, but will not work on production ready, imagine this if a team of 5 devs and then you have support team, the support team in the past would be able to see the network tab, but now that is gone, they would have to understand the code and not really fast to reproduce of debug
American Crow
yea i realize that but that was not the OP question. he was asking for tips
Cuban Crocodile
Seems like they don’t even know how to solve this issue https://x.com/delba_oliveira/status/1768340960964952556?s=46&t=GMXiy8pTs6DUJWLBoKWsnQ
I personally don't know what vercel does to log the network requests but maybe you could do something similar by passing a
NODE_DEBUG=https and then parsing those logs would be one way.@Clown I personally don't know what vercel does to log the network requests but *maybe* you could do something similar by passing a `NODE_DEBUG=https` and then parsing those logs would be one way.
Cuban Crocodile
Any idea of how that would look? I’ve never done anything like that
Cuban Crocodile
Seems like no idea from anyone 🤣