How to solve: Error: ENOENT: no such file or directory , open vite.config.js

[Robbe1910]

I am having a problem when running

npm run dev.

I get the following error:

failed to load config from C:\Users\rober\Documents\GitHub\SPHere-FrontEnd-React\vite.config.js
error when starting dev server:
Error: ENOENT: no such file or directory, open 'C:\Users\rober\Documents\GitHub\SPHere-FrontEnd-React\vite.config.js.timestamp-1716819707025-0719bfc38f1ee.mjs'
    at async open (node:internal/fs/promises:636:25)
    at async Object.writeFile (node:internal/fs/promises:1216:14)
    at async loadConfigFromBundledFile (file:///C:/Users/rober/Documents/GitHub/SPHere-FrontEnd-React/node_modules/vite/dist/node/chunks/dep-C-KAszbv.js:68516:9)
    at async loadConfigFromFile (file:///C:/Users/rober/Documents/GitHub/SPHere-FrontEnd-React/node_modules/vite/dist/node/chunks/dep-C-KAszbv.js:68371:28)
    at async resolveConfig (file:///C:/Users/rober/Documents/GitHub/SPHere-FrontEnd-React/node_modules/vite/dist/node/chunks/dep-C-KAszbv.js:67981:28)
    at async _createServer (file:///C:/Users/rober/Documents/GitHub/SPHere-FrontEnd-React/node_modules/vite/dist/node/chunks/dep-C-KAszbv.js:64503:20)
    at async CAC.<anonymous> (file:///C:/Users/rober/Documents/GitHub/SPHere-FrontEnd-React/node_modules/vite/dist/node/cli.js:762:24)

Previously, it wouldn't even let me install node_modules because it got stuck at idealTree. Finally, after looking for solutions, I decided to downgrade the Node version to 18, and it worked. However, then I got the following error, and it was working fine yesterday. This morning, when I tried to run it, I got the error. I have already tried disabling IPv6 on Windows, deleting package-lock.json and node_modules, and reinstalling, but I get the same error. It's as if temporary files are being created and it tries to find them. If I rename the file to the temporary one it was looking for, the error goes away, but the application doesn't work. I don't know what else to do. If anyone knows how to fix it, I would appreciate your help.
I also tried changing the extension from .js to .mjs and it didn't work.
Another thing I have tried is installing Vite 4.2.2 and its React plugin version 1.0.0, but it didn't work.

If I rename the file to the one it tries to find, I get this error:

Re-optimizing dependencies because lockfile has changed
error when starting dev server:
Error: EPERM: operation not permitted, unlink 'C:\Users\rober\Documents\GitHub\SPHere-FrontEnd-React\node_modules\.vite\deps\@reduxjs_toolkit.js'

However, even if I fix this error, I don't think it will work. The one I want to fix is the ENOENT error.

I managed to fix the last error by deleting the .vite folder, and now it seems to run on localhost, but it keeps loading infinitely and does nothing.

The error lies in the fact that the -timestamp.mjs file does not exist, and it tries to load the configuration from a non-existent file instead of loading it from vite.config.js.

I tried creating a new project from scratch and copying the files, but when I run npm run dev, I get the same error, so it's not an issue with the project.

[himanshuhr8]

is your problem solved as i am stuck with same issue. Please help!

[Robbe1910]

No, sorry. I hope you find a solution soon.

[sriramrudraraju]

It fixed for me when i used vite.config.ts instead .mts

[Owl-in-night]

Español/Spanish: La solución a este problema es bastante simple, debes de descargar una versión similar a la que anteriormente tenías en Node.JS o una que esté relacionada con tu entorno por ejemplo si es para temas de programación la versión LTS funcionan bien, en especial la 18. Como recomendación es preferible antes de hacer un cambio en tu entorno de trabajo tomar nota de todas las versiones importantes de cualquier herramienta de este tipo, para evitar más problemas a futuro. En conclusión la solución a este problema es regresar a la versión anterior de tu Node.JS o cualquier software similar que es necesario en tu proyecto.

Inglés/English:

The solution to this problem is quite simple: you should download a version similar to the one you previously had in Node.JS or one that is related to your environment. For example, if it's for programming purposes, the LTS version works well, especially version 18. It's recommended that before making a change to your work environment, it's preferable to take note of all the important versions of any tool of this type to avoid further problems in the future. In conclusion, the solution to this problem is to return to the previous version of Node.JS or any similar software that is necessary for your project.