Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp'

Current behavior

After running the project via npx nx serve <project_name>, after about 30-40 seconds the process terminates with the error Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp'

here is the full error code:

node:events:496
      throw er; // Unhandled 'error' event
      ^

Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp'
Emitted 'error' event on FSWatcher instance at:
    at FSWatcher._handleError (C:\opm-frontend-main\node_modules\ts-checker-rspack-plugin\node_modules\chokidar\index.js:647:10)
    at NodeFsHandler._boundHandleError (C:\opm-frontend-main\node_modules\ts-checker-rspack-plugin\node_modules\chokidar\lib\nodefs-handler.js:303:43)
    at ReaddirpStream.emit (node:events:518:28)
    at emitErrorNT (node:internal/streams/destroy:169:8)
    at emitErrorCloseNT (node:internal/streams/destroy:128:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -4082,
  code: 'EBUSY',
  syscall: 'lstat',
  path: 'C:\\DumpStack.log.tmp'
}

Node.js v20.12.2
Warning: command "rspack serve --node-env=development" exited with non-zero status code

 NX   Successfully ran target serve for project platform

Environment

• ts-checker-rspack-plugin: 1.1.4
• typescript: 5.8.3
• @rspack/core: 1.3.8
• os: Windows 10

Reproduce the failure on Windows 10 with Node.js 20.12.2 using npx nx serve <project_name>, then inspect the FSWatcher error from chokidar inside ts-checker-rspack-plugin and the rspack serve command. Determine why lstat on C:\DumpStack.log.tmp terminates the process, and verify that the development server remains running without the EBUSY error.