Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Devtools events lost when using Nitro v3 (worker_threads isolates globalThis)

Aberta
  • Algo errado?
#390 2 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
35/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Estagnada
Stack de tecnologia
typescript, vite
Domínio
backend-api-design, devtools

Direção de pesquisa

Comece rastreando EventClient e ServerEventBus em torno de globalThis.TANSTACK_EVENT_TARGET e, em seguida, reproduza o problema com o plugin Vite nitro() e a configuração Nitro v3 worker_threads descrita na issue. Compare os limites entre o worker e a thread principal do Vite e verifique se os eventos do Devtools no lado do servidor chegam ao painel sem o workaround HTTP.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

TanStack Devtools version

0.9.13

Framework/Library version

TanStack Start v1.149.3, Nitro v3.0.1-nightly

Describe the bug and the steps to reproduce it

When using TanStack Start with the nitro() Vite plugin (Nitro v3 nightly) rather than nitroV2Plugin, devtools events emitted from server code never reach the devtools panel.

The root cause is that Nitro v3's NodeEnvRunner runs server code in a worker_threads Worker during dev. EventClient dispatches events to globalThis.__TANSTACK_EVENT_TARGET__
inside the worker thread, but ServerEventBus is listening on a different globalThis.__TANSTACK_EVENT_TARGET__ in the Vite main thread. The events are emitted but never received.

This doesn't happen with nitroV2Plugin because that plugin is build-only — in dev, Start uses its own RunnableDevEnvironment which runs in-process and shares the same global scope.

Steps to reproduce:

  1. Set up a TanStack Start app using nitro() (Nitro v3) instead of nitroV2Plugin
  2. Emit devtools events from server code (e.g. TanStack AI streaming, or any library using @tanstack/devtools-event-client)
  3. Open the devtools panel — server-side events are missing

Workaround:
We confirmed the issue by manually bridging events from the Nitro worker to the Vite process over HTTP — intercepting tanstack-dispatch-event on the worker's
globalThis.__TANSTACK_EVENT_TARGET__ and POSTing the payload to a Vite dev server middleware that re-dispatches it on the main thread's event target. This works but is hacky.

Apologies for the double-post — originally mentioned this in Discord, just filing here too since it might be easier to track.

Your Minimal, Reproducible Example - (Sandbox Highly Recommended)

n/a

Screenshots or Videos (Optional)

No response

Do you intend to try to help solve this bug with your own PR?

None

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.
Linguagem predominante
TypeScript
Estrelas
500
Forks
100
Merge médio
1d 8h
PRs com merge (30d)
4

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de TanStack/devtools

Todas as issues de TanStack/devtools

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.