Query DevTools is not isolated
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 50.3k
- Forks
- 4.2k
- Avg merge
- 18h 25m
- Merged PRs (30d)
- 200
Description
Describe the bug
If we have multiple instances of Query DevTools, actions on one affect the other instance.
Your minimal, reproducible example
https://stackblitz.com/edit/tanstack-react-query-dev-tools-issue?file=README.md
Steps to reproduce
Open the example on the provided link
- Open the devtools
- Click on Query A and Query B to see both dev tools panels (each has its own query client)
- Click on a query on Query A
- Click on a query on Query B
- We see that the previous panel's details are hidden
- Press trigger loading (or any other query option)
- We see the same query details on both panels now
Expected behavior
Each query devtools should be isolated and actions in one should not affect the other one
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
- OS: Linux
- Browser: Brave
Tanstack Query adapter
react-query
TanStack Query version
v5.76.1
TypeScript version
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Run the linked StackBlitz reproduction and confirm that two Query DevTools panels with separate query clients share selection or action state. Trace the Query DevTools instance state involved in selecting queries and triggering loading; done means actions in one panel no longer change the other panel.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- devtools, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100