Unable to the run vue app with latest vite version 2.9.0 and above

[sadashivm]

Describe the bug

Hello team,
I've created a latest vue project using below command,
npm init vue@latest
and project was created, in the latest code vite version installed as
"vite": "^2.9.5".

I tried all the versions from 2.9.0 to 2.9.6, but didn't worked. When run the below command,

npm run dev

I'm getting bellow error,

I tried all the below versions. I got the same above error,

But when I build the application it is working fine. like,

npm run build

Finally I downgraded the vite version to ("vite": "2.8.6"), the app is working properly like,

Reproduction

https://github.com/sadashivm/vue3-latest

System Info

OS - Windows 10,
Node - v16.14.2
npm - 8.7.2

Used Package Manager

npm

Logs

12:58:28 pm [vite] error while updating dependencies:
Error: EPERM: operation not permitted, rename 'D:/Vue/vue3-latest/node_modules/.vite/processing' -> 'D:/Vue/vue3-latest/node_modules/.vite/deps'
    at Object.renameSync (node:fs:980:3)
    at commitProcessingDepsCacheSync (D:\Vue\vue3-latest\node_modules\vite\dist\node\chunks\dep-8db0e223.js:37269:21)
    at Object.commit (D:\Vue\vue3-latest\node_modules\vite\dist\node\chunks\dep-8db0e223.js:37261:13)
    at commitProcessing (D:\Vue\vue3-latest\node_modules\vite\dist\node\chunks\dep-8db0e223.js:58587:34)
    at runOptimizer (D:\Vue\vue3-latest\node_modules\vite\dist\node\chunks\dep-8db0e223.js:58625:17)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

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 https://github.com/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.

[bluwy]

Vite 2.9 has a new prebundling method that does fs.renameSync, which is what the error shows. The relevant code is:

vite/packages/vite/src/node/optimizer/index.ts

Lines 540 to 541 in 274c10e

	removeDirSync(depsCacheDir)
	fs.renameSync(processingCacheDir, depsCacheDir)

We did ensure the .vite/deps is removed before renaming though, so it may be an issue with your system. Perhaps this helps nodejs/node#6335

[patak-dev]

Do you have an Antivirus enabled? I was checking this related node issue: nodejs/node#29481 (comment)

If that is the case, we could add some retry scheme like graceful-fs is using here: https://github.com/isaacs/node-graceful-fs/blob/main/polyfills.js#L88-L116

@bluwy following the issues, it looks like remove dir sync could return before the directory is properly deleted (because of Antivirus or indexing software locking some files). Looks like they tried to bake a fix in libuv and then they reverted it.

[bluwy]

Not a fan of letting these antivirus software "win", but I guess we could implement retries if it's just for this case 😄

[sadashivm]

Yes I have antivirus active

[sadashivm]

Team,
What should I do now?
are you giving any fixes?

[bluwy]

Turn off your antivirus

[sadashivm]

Turn off your antivirus

Sorry to say, this is not correct soultion right?

[bluwy]

I'm not the person for security advice so take my comment with a grain of salt, but I've never quite find antivirus software to be really helpful as long as you're browsing safely and only install software you trust. Plus modern browsers all have solid first line of defence to protect you from it. It's worked for me and I never had issues on my machines (windows/linux/mac).

If you're on Windows, you can turn on Windows Defender and remove any other antivirus software. That has worked well even for my 8yo brother who randomly installs stuff 🥲

[mattnathan]

I'm having the same issue. As an experiment I disabled the virus check for my project folder (and sub-folders) but that didn't seem to have an effect.

When I run the vite dev server and check the node_module/.vite folder I see an empty deps folder, and a processing folder with all the lib files in it.

Using vite@2.9.6

[patak-dev]

@mattnathan @sadashivm would you test vite@2.9.8 in your projects and report back? Thanks!