--stats-error-details true causes webpack to never exit if cache is used

[radex]

Bug report

What is the current behavior?

If all of these conditions are true:

• cache: { type: 'filesystem', ... } option is used
• the cache is fresh
• --stats-error-details true is passed to CLI

Then webpack will never complete, and will get stuck after the final "success" log:

(... more stats ...)
Entrypoint main 56.9 KiB (293 KiB) = static/runtime~main.bundle.89bd23eb.js 1.53 KiB static/vendors.bundle.ecaefaad.js 55.1 KiB static/main.bundle.60c2d488.js 340 bytes 3 auxiliary assets
cached modules 359 KiB (javascript) 3.71 KiB (runtime) [cached] 63 modules
webpack 5.23.0 compiled successfully in 2876 ms
^[[A^C

Dirtying app files, removing cache config, or removing the debug --stats-error-details true command fixes the issue

If the current behavior is a bug, please provide the steps to reproduce.

Same as above ⬆️.

What is the expected behavior?

webpack does not get stuck forever :) and either cleanly exits or reports an error

Other relevant information:
webpack version: 5.23.0
Node.js version: 12.20.2
Operating System: macOS 10.15.7
Additional tools: n/a

[webpack-bot]

For maintainers only:

• webpack-4
• webpack-5
• bug
• critical-bug
• enhancement
• documentation
• performance
• dependencies
• question

[radex]

Update: Nope, I was sure that this was the cause of webpack getting stuck, but turns out I can still reproduce it, and can't find the root cause...

[taylorthurlow]

FWIW I am also having this no-exit-after-success problem, haven't pinned it down yet.

EDIT: For me this was a problem with tailwindcss/jit running a file watcher when I didn't expect it to, with no logged output

[maclockard]

I run into this if I set stats.all to false

EDIT:
Filed here: #12976