Vite "watch" hangs after first change since v4.2

[Diggsey]

Describe the bug

I run:

vite build --watch --minify false --mode development

The build completes successfully. I then make a change to a file, triggering a rebuild. The rebuild will hang after printing:

build started...

Sometimes it will print an additional line like :

build started...
transforming (xxx)  <filename>

But there doesn't appear to be any correlation between the filename and the build, it's just a random file from the project.

Reproduction

Diggsey/dpass@8badbb0

Steps to reproduce

Clone the repo and install dependencies as usual for an npm project. Run:

vite build --watch --minify false --mode development

Save any file triggering a rebuild.

System Info

System:
    OS: Windows 10 10.0.19045
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i9-12900H
    Memory: 15.86 GB / 31.68 GB
  Binaries:
    Node: 18.12.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 9.2.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (112.0.1722.39)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    vite: ^4.2.0 => 4.2.0

(Also reproduced on linux.)

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[Diggsey]

Based on the changelog, I am suspicious of #11908

[Diggsey]

I've also tried enabling logging and debug output, but vite outputs nothing useful. This seems like a bug in and of itself: vite should really provide some output logs that can be used to diagnose issues like this...

[bluwy]

Duplicate of #12791. Fixed in #12797