Solid.js 'multiple instances' warnings appear in React apps with Vite 8
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 499
- Forks
- 100
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 4
Description
TanStack Devtools version
@tanstack/react-devtools v0.10.1, @tanstack/devtools-vite v0.6.0
Framework/Library version
React 19.2.4, TanStack Start 1.167.16, Vite 8.0.3
Describe the bug and the steps to reproduce it
When using TanStack Devtools in a React TanStack Start app with Vite 8, the following warnings appear in the terminal and browser when starting the dev server
❯ bun run dev
$ vite dev --port 3000
VITE v8.0.3 ready in 1039 ms
➜ Local: http://localhost:3000/
➜ Network: use --host to expose
➜ press h + enter to show help
[vite] connected.
9:48:32 AM [vite] (client) [console.warn] You appear to have multiple instances of Solid. This can lead to unexpected behavior.
9:48:32 AM [vite] (client) [console.warn] You appear to have multiple instances of Solid. This can lead to unexpected behavior.
9:48:32 AM [vite] (client) [console.warn] computations created outside a `createRoot` or `render` will never be disposed
9:48:32 AM [vite] (client) [console.warn] computations created outside a `createRoot` or `render` will never be disposed
9:48:32 AM [vite] (client) [console.warn] cleanups created outside a `createRoot` or `render` will never be run
9:48:32 AM [vite] (client) [console.warn] computations created outside a `createRoot` or `render` will never be disposed
9:48:32 AM [vite] (client) [console.warn] computations created outside a `createRoot` or `render` will never be disposed
9:48:32 AM [vite] (client) [console.warn] cleanups created outside a `createRoot` or `render` will never be run
9:48:32 AM [vite] (client) [console.warn] computations created outside a `createRoot` or `render` will never be disposed
9:48:32 AM [vite] (client) [console.warn] cleanups created outside a `createRoot` or `render` will never be run
9:48:32 AM [vite] (client) [console.warn] cleanups created outside a `createRoot` or `render` will never be run
9:48:32 AM [vite] (client) [console.warn] computations created outside a `createRoot` or `render` will never be disposed
These warnings do not appear with Vite 7 using the exact same dependencies and configuration.
Steps to reproduce:
- Clone the repro repo and install dependencies:
git clone https://github.com/abed-daloopa/tanstack-devtools-solid-warnings cd tanstack-devtools-solid-warnings bun install - Run the dev server:
bun run dev - Open http://localhost:3000 — warnings appear in the browser console and terminal.
To verify Vite 8 is the cause, downgrade to Vite 7:
- "vite": "^8.0.3"
+ "vite": "^7.3.1"
Or add resolve.dedupe: ["solid-js"] to vite config
Reinstall and run ➡︎ warnings disappear.
Root cause: Vite 8 resolves Solid.js as multiple instances at runtime, even when only one copy exists in node_modules. Vite correctly deduplicates it.
Note: Adding resolve.dedupe: ["solid-js"] to the Vite config fixes the issue.
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
https://github.com/abed-daloopa/tanstack-devtools-solid-warnings
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
Maybe
Terms & Code of Conduct
- I agree to follow this project's Code of Conduct
- I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
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
Start with the linked minimal reproduction and its Vite configuration, then compare the dev-server behavior under Vite 7 and Vite 8. Inspect the TanStack devtools Vite integration and the reported Solid.js resolution path; done means the Vite 8 setup no longer emits the duplicate-instance and disposal warnings without relying on the reported dedupe workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript, vite
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100