koba04 / swr-devtools

A DevTool for SWR
https://swr-devtools.vercel.app
MIT License
217 stars 3 forks source link

doesn't work in nextjs13 project with chrome #128

Open QingjiaTsang opened 8 months ago

QingjiaTsang commented 8 months ago

using nextjs@13.4 and swr@2.2.2

I wrapped the SWRDevTools at the top client component and there's no errors up in chrome console, but it seems nothing happened at the swr panels when I fetch some data.

Is it supported in nextjs app?

koba04 commented 8 months ago

Yes, I think SWRDevTools should work with Next v13. In this case, you don't wrap your application with <SWRDevTools />

https://github.com/koba04/swr-devtools#how-to-use

I expect you can see cache data on the SWRDevTools panel only by installing a SWRDevTools extension. Could you reload the page while opening the SWRDevTools panel if you can't see data on the panel?

https://github.com/koba04/swr-devtools#install-the-swrdevtools-extension

fgascon commented 8 months ago

We use next.js v13.5.3 and it didn't work as well. When adding <SWRDevTools /> in our layout it worked.

I've seen in the examples you have one using v13.1.6, so maybe it's a more recent change to next.js which broke the SWRDevTools automatic injection.

koba04 commented 8 months ago

Thank you! I'll update the Next version to the latest and test it.

koba04 commented 8 months ago

I can reproduce it and will try to fix it. Sometimes, the SWRDevTools display cache data correctly, so I assume a connection problem between an application and the Chrome extension process causes this.

pvaladez commented 6 months ago

Using Chrome v120 I'm not able to get it working with or without the <SWRDevTools> component wrapping my app. It also doesn't work at https://swr-devtools.vercel.app/.

However, it does work in Firefox.

gary-lo commented 5 months ago

Any updates?

BeezBeez commented 5 months ago

Hello, any updates on this issue? I'm experimenting the same problem.

st33b commented 3 months ago

Since it works as expected in Firefox, perhaps the issue is with the Chrome extension?

koba04 commented 3 months ago

The Firefox version is still MV2, but the Chrome version is MV3, so I assume the MV3 implementation is incorrect.

Mandy9943 commented 1 week ago

is not working either on edge, maybe the same reason not working on chrome