Concurrency issue with `prepareVueTsc` function

[kitsune7]

Describe the bug

When running Vite's dev server in a monorepo with a micro-frontend architecture (multiple apps need to run at once to load different pages and sections of the site), prepareVueTsc is called multiple times in parallel. This causes errors.

I believe most of the issues step from the logic inside the if (shouldBuildFixture) block, which is in the prepareVueTsc function.

Not a ton of people use the kind of architecture that would run this function several times in parallel, but it highlights an issue where this logic really just needs to run once after dependencies have been installed. I can get around the issue by just running a single app by itself long enough for the plugin to get the right files set up in node_modules, but in a project with a large number of contributors, this problem adds a lot of extra friction to the setup.

Could we maybe have a postinstall script that runs this logic? Or if not, maybe we can implement a file-based mutex lock to prevent file conflicts?

Reproduction

1. Run npm install (or the equivalent command for your package manager) on a project that runs vite-plugin-checker with Vite's dev server
2. Ensure that the project uses npm workspaces (or a similar equivalent for other package managers) where multiple apps use the same base node_modules directory
3. Run npm run dev for each app so that they start in parallel

Expected behavior

vite-plugin-checker has the ability to be run in parallel without issues after it's installed to node_modules. Any typescript issues are logged to the console.

System Info

System:
    OS: macOS 15.6
    CPU: (12) arm64 Apple M3 Pro
    Memory: 5.63 GB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.14.0 - ~/.nvm/versions/node/v22.14.0/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 11.5.2 - /opt/homebrew/bin/npm
    pnpm: 10.13.1 - /opt/homebrew/bin/pnpm
    bun: 1.2.2 - ~/.bun/bin/bun
  Browsers:
    Safari: 18.6
  npmPackages:
    vite-plugin-checker: ^0.10.2 => 0.10.2

Additional context

Here are some of the errors that I see when running things in parallel:

node:internal/event_target:1101
  process.nextTick(() => { throw err; });
                           ^
[Error: ENOTEMPTY: directory not empty, rmdir '<my_project_path>/node_modules/vite-plugin-checker/dist/checkers/vueTsc/typescript-vue-tsc/lib'] {
  errno: -66,
  code: 'ENOTEMPTY',
  syscall: 'rmdir',
  path: '<my_project_path>/node_modules/vite-plugin-checker/dist/checkers/vueTsc/typescript-vue-tsc/lib'
}

node:internal/event_target:1101
  process.nextTick(() => { throw err; });
                           ^
Error: ENOENT: no such file or directory, copyfile '/<my_project_path>/node_modules/typescript/lib/typesMap.json' -> '/<my_project_path>/node_modules/vite-plugin-checker/dist/checkers/vueTsc/typescript-vue-tsc/lib/typesMap.json'
    at async copyFile (node:internal/fs/promises:620:10)
    at async _copyFile (node:internal/fs/cp/cp:260:3)
    at async copyDir (node:internal/fs/cp/cp:320:19)
    at async mkDirAndCopy (node:internal/fs/cp/cp:309:3)
    at async copyDir (node:internal/fs/cp/cp:320:19)
    at async prepareVueTsc (file:///<my_project_path>/node_modules/vite-plugin-checker/dist/checkers/vueTsc/prepareVueTsc.js:44:5)
    at async Object.configureServer (file:///<my_project_path>/node_modules/vite-plugin-checker/dist/checkers/vueTsc/main.js:36:31) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'copyfile',
  path: '/<my_project_path>/node_modules/typescript/lib/typesMap.json',
  dest: '/<my_project_path>/node_modules/vite-plugin-checker/dist/checkers/vueTsc/typescript-vue-tsc/lib/typesMap.json'
}

Validations

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

[kitsune7]

We've had to use some interesting workarounds to avoid needing to write the functionality for this ourselves. But it's definitely still an issue.

[npbenjohnson]

Could you post an example workaround? Do you somehow pre-hydrate the vue-tsc checker? I'm hitting the same thing with vitest and I'm having trouble coming up with a workaround.

[michal-sarzala-pm]

Any updates on this?

[kiritsu0]

While running yarn build in CI with multiple workspaces executed in parallel, I encountered a race condition related to vue-tsc.

When several workspace builds start simultaneously, each of them invokes vue-tsc (via vite-plugin-checker). Internally this leads to concurrent writes to the same generated file in:
node_modules/.vue-global-types/vue_3.5_0_0_0.d.ts

As a result, the file occasionally ends up in a corrupted state, and TypeScript fails with syntax errors such as:

error TS1110: Type expected
error TS1005: ':' expected
error TS1005: '>' expected
error TS1005: '?' expected

Does this align with the issue described here? If so, are there any recommended workarounds for CI setups (besides disabling vue-tsc 😂)

[kitsune7]

@npbenjohnson Sorry, I totally your message asking for workarounds! We use pnpm in our monorepo and we added a function to .pnpmfile.cjs that looks similar to this (with the ANY_WORKSPACE variable swapped out) and have it run in the afterAllResolved hook.

function fixVitePluginCheckerInstall() {
  try {
    const { prepareVueTsc } = require('./node_modules/vite-plugin-checker/dist/checkers/vueTsc/prepareVueTsc.js');
    prepareVueTsc().then(() => {
      console.log('[vite-plugin-checker] vueTsc prepared once after install');
    });
  } catch (err) {
    console.error('[vite-plugin-checker] Failed to prepare vueTsc:', err);
    console.log(
      '[vite-plugin-checker] You can fix the issue manually by running "pnpm --filter "${ANY_WORKSPACE}" dev" and closing the process shortly after it shows the port it\'s running on.',
    );
  }
}

Running a single workspace by itself and then ending the dev server after it's had just a moment to run fixes the problem, but you can also just use a Node.js script that runs prepareVueTsc to fix the issue.