Pre-bundled client ignores the event bus port from devtools-vite
I maintainer di solito rispondono entro 1 giorno
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 76/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- react, typescript, vite
- Ambito
- build-system, devtools, networking
Direzione di ricerca
Start with the connection-injection transform, using the vite.config.ts and src/main.tsx reproduction described in the issue. Run the Vite app with a non-default event bus port and inspect the served /node_modules/.vite/deps chunk; done means the pre-bundled client uses the configured or fallback port and connects to the server bus.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
TanStack Devtools version
@tanstack/react-devtools 0.10.13, @tanstack/devtools-vite 0.8.5
Framework/Library version
React 19.3.0, Vite 8.3.1
Describe the bug and the steps to reproduce it
In the browser, the event bus client always uses port 4206, even when devtools-vite runs the server bus on another port. So eventBusConfig.port in devtools() has no effect in the browser. The EADDRINUSE fallback fails the same way. When another dev server holds 4206, the plugin moves its own bus to a random port. The browser still dials 4206.
Cause
The @tanstack/devtools:connection-injection transform replaces __TANSTACK_DEVTOOLS_PORT__ only in modules whose id contains @tanstack/devtools or @tanstack/event-bus. Vite pre-bundles @tanstack/react-devtools and serves the bus client from a chunk such as /node_modules/.vite/deps/BRS44MK7-KeTQTbh5.js. That id matches neither filter, so the placeholder stays, and getDefaultPort(4206) returns 4206.
The examples in this repository link the packages with workspace:*, and Vite does not pre-bundle linked packages.
Reproduction
package.json dependencies:
"@tanstack/devtools-vite": "0.8.5",
"@tanstack/react-devtools": "0.10.13",
"@vitejs/plugin-react": "6.1.1",
"react": "19.3.0",
"react-dom": "19.3.0",
"vite": "8.3.1"
vite.config.ts:
import { devtools } from '@tanstack/devtools-vite'
import react from '@vitejs/plugin-react'
import { defineConfig } from 'vite'
export default defineConfig({
plugins: [devtools({ eventBusConfig: { port: 4260, debug: true } }), react()],
})
src/main.tsx, loaded from a plain index.html:
import { TanStackDevtools } from '@tanstack/react-devtools'
import { createRoot } from 'react-dom/client'
createRoot(document.getElementById('root')!).render(
<TanStackDevtools eventBusConfig={{ connectToServerBus: true, debug: true }} />,
)
-
Run
vite --port 3160. The server bus starts on the configured port:🌴 [tanstack-devtools:server-bus] Listening on http://localhost:4260 -
Open http://localhost:3160/. The client fails to connect, and the server bus logs no client:
[Client] 🌴 [tanstack-devtools:client-bus] Connecting to WebSocket server [Client] 🌴 [tanstack-devtools:client-bus] WebSocket connection error -
Fetch the served chunk that contains the bus client, for example
curl -s 'http://localhost:3160/node_modules/.vite/deps/BRS44MK7-KeTQTbh5.js'. The placeholder is still there:function getDefaultPort(configPort) { if (typeof __TANSTACK_DEVTOOLS_PORT__ !== "undefined") return __TANSTACK_DEVTOOLS_PORT__; return configPort; }
As a control, add optimizeDeps: { exclude: ['@tanstack/react-devtools'] }. The server bus then logs New WebSocket client connected, and the client logs WebSocket connection opened. This exclusion is not a usable workaround, because it breaks the dayjs default import (#423).
Expected behavior
The browser client connects to the port the server bus listens on, including the EADDRINUSE fallback port.
Workaround
Pass the same fixed port to both sides: devtools({ eventBusConfig: { port } }) and <TanStackDevtools eventBusConfig={{ port }} />. This fails again when that port is taken.
Possible fix
Also match ids under /node_modules/.vite/deps/ in connection-injection. The placeholder check already limits the transform to modules that contain the placeholders.
Environment: macOS (Darwin 25.6.0), Bun 1.4.2, Node 26.10.0, Chrome.
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
The complete reproduction is inline above: four files and three steps.
Do you intend to try to help solve this bug with your own PR?
Yes, I think I know how to fix it and will discuss it in the comments of this issue
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.
- Lingua principale
- TypeScript
- Stelle
- 503
- Fork
- 102
- Merge medio
- 1g 8h
- PR unite (30g)
- 4
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di TanStack/devtools
-
`intent` bin conflicts with @tanstack/intent and imports removed subpathForse già presa @AlemTuzlak l’ha presa 10 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
TanStack/devtools#525 · 2 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
devtools-ui 0.7.0 breaks SSR boot with solid-js <=1.9.12: `use` is not exported by solid-js/web server buildForse già presa @AlemTuzlak l’ha presa 10 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
data-tsd-source inject-source plugin causes hydration mismatch in SSR (TanStack Start)Forse già presa @AlemTuzlak l’ha presa 9 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
TanStack/devtools#405 · 4 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 52/100
I maintainer di solito rispondono entro 1 giorno
-
Devtools breaks react-resizable-panels cursor after remountForse già presa @AlemTuzlak l’ha presa 9 giorni fa. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di TanStack/devtools
Issue simili
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: [A11y] Missing accessible name on icon-only standalone links (WCAG 2.1 SC 2.4.4, 4.1.2)Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
jaegertracing/jaeger-ui#4596 ·
I maintainer di solito rispondono entro 1 giorno
-
area:tui enhancement platform:macos
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
anthropics/claude-code#101490 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
netlify/netlify-mcp#75 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno