koba04/swr-devtools

After a short period of time, Cache and History tabs stop updating

Open

#110 opened on Dec 20, 2022

View on GitHub
 (2 comments) (0 reactions) (0 assignees)TypeScript (219 stars) (4 forks)user submission
bughelp wanted

Description

I'm not sure what the exact issue is, but I just started using SWR and the devtools, and I've noticed that I have to close and re-open my devtools pane after maybe ~30 minutes/1 hour because the Cache and History tabs stop receiving updates.

I'm on version 2.0.0 of swr and 1.2.0 of the devtools installed on Chrome 108.0.5359.124.

Is there any known issue with this? Let me know if there's more info I can provide to help. When I open the devtools for the extension's service worker I don't see any errors, and I still see the pane connection events being logged even when the SWR devtools pane stops updating.

Contributor guide

Tech stack
typescriptreact
Domain
developer experiencetoolingfrontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Familiarity with Chrome extensionsUnderstanding of SWR libraryBasic React knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the communication between the devtools panel and the service worker to understand why updates stop after ~30-60 minutes. Focus on the messaging layer (e.g., chrome.runtime.connect or port.postMessage) and any reconnection logic. Check the panel component for state updates and see if there is a timeout or cleanup issue. Look at recent commits or linked issues for similar reports. The issue mentions that pane connection events are still logged when the panel stops updating, so the connection itself may remain open but data flow halts. Possibly related to object garbage collection or stale closures.