Tests closed successfully but something prevents Vite server from exiting
Mantenedores costumam responder em até 1 dia
@liangmiQwQ já está trabalhando nisso.
Desde 27/10/2026.
Avaliação
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Facilidade para iniciantes
- 56/100
- Tipo de issue
- Bug
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Stack de tecnologia
- bun, typescript, vite
Direção de pesquisa
Start with the Vite+ vp test related command and its Vitest shutdown or cleanup path; the issue does not name a source file or failing test. Reproduce with bun install and the reported vp test related --run src/App.tsx src/components/Counter.test.tsx command, then use Vitest’s hanging-process reporter to locate what keeps the server alive. Done when the command exits successfully after the tests finish.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Describe the bug
vp test related --run src/App.tsx src/components/Counter.test.tsx
note: You are running `vp test` as a Vite+ built-in command. If you meant to run the test npm script, use `vpr test` instead.
RUN v5.0.5 /home/ian/templates/react-template
stdout | unknown test
shift + ⌥option + left click to use active feature
stdout | unknown test
shift + ⌥option + right click to open node tree
stdout | unknown test
shift + ⌥option + mouse wheel to select parent node or child node
stdout | unknown test
shift + ⌥option + Z to change active feature
stdout | unknown test
shift + ⌥option + 1 to use Locate Code
stdout | unknown test
shift + ⌥option + 2 to use Copy Path
stdout | unknown test
shift + ⌥option + 3 to use Open Target
stdout | unknown test
shift + ⌥option + 4 to use AI Assistant
✓ chromium src/components/Counter.test.tsx (3 tests) 87ms
✓ Counter (3)
✓ renders default initial count 15ms
✓ renders count from init prop 3ms
✓ increments count after button click 68ms
Test Files 1 passed (1)
Affected 1 of 4 test files (related to 2 files)
Tests 3 passed (3)
Start at 22:44:15
Duration 1.39s (import 44%, tests 28%, worker 27%)
close timed out after 10000ms
Tests closed successfully but something prevents Vite server from exiting
You can try to identify the cause by enabling "hanging-process" reporter. See https://vitest.dev/guide/reporters.html#hanging-process-reporter
this would also stuck git hooks.
Reproduction
https://github.com/ianzone/react-template
Steps to reproduce
Run bun install followed by vp test related --run src/App.tsx src/components/Counter.test.tsx
System Info
vp env current
✔ Would you like Vite+ to manage your Node.js and package-manager versions? · no
Setup:
Preparing vite-plus environment.
Created Shims:
/home/ian/.local/share/vite-plus/fallback-bin/node
/home/ian/.local/share/vite-plus/fallback-bin/npm
/home/ian/.local/share/vite-plus/fallback-bin/npx
/home/ian/.local/share/vite-plus/fallback-bin/pnpm
/home/ian/.local/share/vite-plus/fallback-bin/pnpx
/home/ian/.local/share/vite-plus/fallback-bin/pn
/home/ian/.local/share/vite-plus/fallback-bin/pnx
/home/ian/.local/share/vite-plus/fallback-bin/yarn
/home/ian/.local/share/vite-plus/fallback-bin/yarnpkg
/home/ian/.local/share/vite-plus/fallback-bin/bun
/home/ian/.local/share/vite-plus/fallback-bin/bunx
/home/ian/.local/share/vite-plus/bin/vpx
/home/ian/.local/share/vite-plus/bin/vpr
Next Steps:
For Zsh, run:
. "/home/ian/.config/vite-plus/env"
If your .zshrc does not already load Vite+, add this command.
Restart an already-running IDE to load its environment. Run `vp env doctor` to verify.
✓ Vite+ setup complete.
VITE+ - The Unified Toolchain for the Web
Node.js:
Version 24.21.0
Source system PATH
Bin Path /run/user/1000/fnm_multishells/33240_1793020172470/bin/node
Installed true
Mode system_first
Package Manager:
Name bun
Version 1.4.4
Source system PATH
Bin Paths
bun /home/ian/.bun/bin/bun
bunx /home/ian/.bun/bin/bunx
Installed true
Mode system_first
vp --version
VITE+ - The Unified Toolchain for the Web
vp v1.4.0
Local vite-plus:
vite-plus v1.4.0
Tools:
vite v8.3.5
rolldown v1.2.15
vitest v5.0.5
oxfmt v0.74.0
oxlint v1.89.0
oxlint-tsgolint v7.0.2004
tsdown v0.23.1
Environment:
Package manager bun default
Node.js v24.22.1
Used Package Manager
bun
Logs
Validations
- Read the Contributing Guidelines.
- Check that there isn't already an issue for the same bug.
- Confirm this is a Vite+ issue and not an upstream issue (Vite, Vitest, tsdown, Rolldown, or Oxc).
- The provided reproduction is a minimal reproducible example.
- Linguagem predominante
- Rust
- Estrelas
- 6.5k
- Forks
- 296
- Merge médio
- 1d 2h
- PRs com merge (30d)
- 230
Preparar o ambiente
Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.
- Sem Dockerfile nem arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de voidzero-dev/vite-plus
-
pending triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 63/100
voidzero-dev/vite-plus#3235 ·
Mantenedores costumam responder em até 1 dia
-
Docker guide: the runtime stage needs libatomic1 for Node.js 25 and laterTalvez já em andamento @kshanxs assumiu há 5 dias. Abertadocumentation
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
voidzero-dev/vite-plus#3219 · 2 comentários · 1 reação ·
Mantenedores costumam responder em até 1 dia
-
pending triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
voidzero-dev/vite-plus#2882 · 2 comentários ·
Mantenedores costumam responder em até 1 dia
-
`vp create` doesn't rewrite `vite` imports when adding a third-party template to a monorepoTalvez já em andamento @voidzero-bot assumiu hoje. Aberta- P2: has workaround pending triage triage: fix verified
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 35/100
voidzero-dev/vite-plus#3281 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
`npm install -g` keeps the `bin` link on the old version after the default Node.js changesTalvez já em andamento @mondaychen assumiu hoje. Abertabug triage: failed
voidzero-dev/vite-plus#3279 · 1 comentário · 1 responsável ·
Mantenedores costumam responder em até 1 dia
Todas as issues de voidzero-dev/vite-plus
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 83/100
Mantenedores costumam responder em até 1 dia
-
priority middle
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 62/100
KATO-Hiro/AtCoderClans#12940 ·
Mantenedores costumam responder em até 1 dia
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 83/100
Mantenedores costumam responder em até 1 dia
-
o8 next debug build aborts on Glass to Dark appearance switch (nil identifier messaged before check)Abertabug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
hurttlocker/o8#5112 ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 79/100
Mantenedores costumam responder em até 1 dia