Vite dev watcher breaks with "EBUSY: resource busy or locked"

[Joelsz]

Describe the bug

Hi, I'm using Vite to build a Cloudflare Pages project. When starting the dev server it always fails with the following error, sometimes immediately sometimes after a few file changes.

As per #13234 this should've been fixed in 5.0.0, however, it still breaks here.

npx vite -v
vite/5.4.11 win32-x64 node-v22.12.0`

npx vite dev

  VITE v5.4.11  ready in 14166 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose
  ➜  press h + enter to show help
node:events:502
      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 (file:///C:/Users/user/dev/project-name/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:44480:10)
    at NodeFsHandler._boundHandleError (file:///C:/Users/user/dev/project-name/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:42953:43)
    at ReaddirpStream.emit (node:events:524:28)
    at ReaddirpStream.emit (node:domain:489:12)
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
  errno: -4082,
  code: 'EBUSY',
  syscall: 'lstat',
  path: 'C:\\DumpStack.log.tmp'
}

Node.js v22.12.0

This is my vite.config.ts:

import pagesBuild from '@hono/vite-cloudflare-pages'
import adapter from '@hono/vite-dev-server/cloudflare'
import honox from 'honox/vite'
import client from 'honox/vite/client'
import { defineConfig } from 'vite'

export default defineConfig(({ mode }) => {
  let options;
  if (mode === 'client') {
    options = {
      build: {
        rollupOptions: {
          input: ['/app/style.css'], 
          output: {
            assetFileNames: 'static/assets/[name].[ext]'
          }
        },
      },
      plugins: [client()]
    }
  } else {
    options = {
      plugins: [
        honox({
          devServer: {
            adapter
          }
        }),
        pagesBuild()
      ]
    }
  }
  return options;
})

Reproduction

https://github.com/lauragift21/staff-directory/

Steps to reproduce

Run npm install followed by npx vite dev.

Wait for the server to start up, then proceed to making some file changes.

System Info

System:
    OS: Windows 11 10.0.26100
    CPU: (12) x64 13th Gen Intel(R) Core(TM) i7-1365U
    Memory: 2.47 GB / 15.35 GB
  Binaries:
    Node: 22.12.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.9.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (129.0.2792.79)
    Internet Explorer: 11.0.26100.1882
  npmPackages:
    vite: ^5.0.12 => 5.4.11

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.

[hi-ogawa]

We had a report on Vitest vitest-dev/vitest#5740 and this seems to due to some virtual module path (e.g. /@react-refresh by react plugin).

[Joelsz]

Interestingly enough, adding the following ignoreWatching to the config fixed the issue for now.

devServer: {
  ignoreWatching: ['*', /\.wrangler/],
  adapter
}