@mklueh I think you should submit a minimal reproduction. Can you submit it?

If it's happening with Nuxt, it's probably related to a dependency we share... Maybe Chokidar? What versions of chokidar are listed in your lockfile?

Good point. I was on chokidar 3.6.0 before, and now I've enforced 4.0.1 but facing the same problem

Haven't faced it with Nuxt anymore for a while now, but the Wxt issue remains. Are you guys developing on Windows?

I don't have a windows machine. Did Nuxt have an issue for this that got closed that we can reference?

i developed on windows 11, my package.json

{
  "name": "@downloader/plugin",
  "private": true,
  "version": "0.1.0",
  "type": "module",
  "scripts": {
    "dev": "wxt",
    "dev:firefox": "wxt -b firefox",
    "build": "wxt build",
    "build:firefox": "wxt build -b firefox",
    "zip": "wxt zip",
    "zip:firefox": "wxt zip -b firefox",
    "compile": "vue-tsc --noEmit",
    "clean": "rimraf dist",
    "postinstall": "wxt prepare"
  },
  "dependencies": {
    "@types/chrome": "^0.0.268",
    "pinia": "^2.3.0",
    "vue": "^3.5.13"
  },
  "devDependencies": {
    "@vitejs/plugin-vue": "^5.2.1",
    "axios": "^1.7.9",
    "rimraf": "^5.0.10",
    "sass": "^1.83.0",
    "typescript": "^5.7.2",
    "unocss": "^0.60.4",
    "unplugin-icons": "^0.22.0",
    "vite": "^5.4.11",
    "vite-plugin-vue-devtools": "^7.6.8",
    "vue-tsc": "^1.8.27",
    "wxt": "^0.17.12"
  }
}

This is my project structure. In the entrypoints, only content is the code I actually developed. When I modify the code in content/App.vue, this issue almost always occurs, but I can't determine the exact timing or cause.

i developed on windows 11, my package.json

{
  "name": "@downloader/plugin",
  "private": true,
  "version": "0.1.0",
  "type": "module",
  "scripts": {
    "dev": "wxt",
    "dev:firefox": "wxt -b firefox",
    "build": "wxt build",
    "build:firefox": "wxt build -b firefox",
    "zip": "wxt zip",
    "zip:firefox": "wxt zip -b firefox",
    "compile": "vue-tsc --noEmit",
    "clean": "rimraf dist",
    "postinstall": "wxt prepare"
  },
  "dependencies": {
    "@types/chrome": "^0.0.268",
    "pinia": "^2.3.0",
    "vue": "^3.5.13"
  },
  "devDependencies": {
    "@vitejs/plugin-vue": "^5.2.1",
    "axios": "^1.7.9",
    "rimraf": "^5.0.10",
    "sass": "^1.83.0",
    "typescript": "^5.7.2",
    "unocss": "^0.60.4",
    "unplugin-icons": "^0.22.0",
    "vite": "^5.4.11",
    "vite-plugin-vue-devtools": "^7.6.8",
    "vue-tsc": "^1.8.27",
    "wxt": "^0.17.12"
  }
}

This is my project structure. In the entrypoints, only content is the code I actually developed. When I modify the code in content/App.vue, this issue almost always occurs, but I can't determine the exact timing or cause.

In my project, I suspect the issue might be related to Unocss, but the root cause could involve Vite or some deeper underlying mechanisms.

Here are relevant issues that provide some temporary solutions:

• 频繁出现报错 resource busy or locked, lstat 'C:\DumpStack.log.tmp' dcloudio/uni-app#3603
• Running the dev tools on Windows causes Vite to fail due to watching / crxjs/chrome-extension-tools#538

Temporary Solutions for Reference

1. Switch from Unocss to TailwindCSS.
   I tested several projects based on WXT, Vite, and Unocss that I found on GitHub. All of them eventually triggered this issue after running for some time on my machine. However, when I switched from Unocss to TailwindCSS, the issue did not reappear.

2. Identify the error-causing code and skip the related errors.

_handleError(error) {
  const code = error && error.code;
  if (error && code !== 'ENOENT' && code !== 'ENOTDIR' &&
    (!this.options.ignorePermissionErrors || (code !== 'EPERM' && code !== 'EACCES'))
  ) {
    const filePath = 'C:\\DumpStack.log.tmp';
    if (error.code === "EBUSY" && error.path === filePath) {
        return error;
    }
    this.emit(EV_ERROR, error);
  }
  return error || this.closed;
}