-
-
Notifications
You must be signed in to change notification settings - Fork 6.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There will be temporary vite.config.js.timestamp files that have not been cleaned up #13267
Comments
Start a new pull request in StackBlitz Codeflow. |
Related to this, these files should not be generated within the project root. Their existence causes race conditions when running multiple build/lint/type-checking/etc processes simultaneously. Here's a sample error from my CI/CD output.
|
Having the same issue using this Chrome Extension vite template |
Organizing the issues with the approach with using
|
…outlined in vitejs/vite#13267 It would occassionally cause the Svelte server to restart in an infinite loop as the temporary file created would trigger Meteor to do a restart, which in turn would create a new temporary file.
Same here. Is there a way to set location of it somewhere in |
this is need could these files be created in |
Same problem here: we have a plugin that is loaded in vite to inject git hash in the build, So it fails because the git directory non clean at that time. Workaround was to add an exclusion in gitignore. |
i didnt get the solution,same issue at my production level |
I solved this issue. vite.config.ts.timestamp-* generates in node 16 version, node 20 version.
In my package.json,_ "scripts": { "build": "tsc && rm -rf dist/vite.config.ts.timestamp-* && vite build", } Note that : Same way I tried in node 16, 20 version, it didnt worked, but finally worked for node 18 version which stops generating timestamp and deployed to production in my pm2. |
These temporary files also cause
|
also having this issue on node v21, i'm running |
I think a related issue I'm having to this one.. For me vite.config.mts is building in a loop, or vite.config.ts does if I specify type: module in package.json So going to go back to seeing the deprecated warnings since it doesn't do this with vite.config.ts |
Having this issue when I try to run a Vite+Svelte project with PM2 |
This (or something similar) happens regularly when eg. the Vite dev server is running while doing a This might be a separate bug though, because this happens due to |
My process is simple:I have added it to my
And I've created a script to delete these files on my main
{
"scripts": {
"clean": "find . -type f -name 'vite.config.*.timestamp-*' -ls -delete 2>/dev/null"
}
} Then I run
and ✨ gone! |
Probably partially related, but sometimes in error TS6053: File 'package/package/vite.config.package.ts.timestamp-1710918996371-a57b80255a0c5.mjs' not found.
The file is in the program because: |
I got same problem! |
The files will also cause a problem with my setup because I am using [warn] vite.config.ts.timestamp-1711554296877-215d5766798.mjs
html-ui:lint: [warn] Code style issues found in the above file. Run Prettier to fix. vite.config.ts.timestamp-1711553549825-4b69edd70157b.mjs
html-ui:lint: [error] Unable to read file "vite.config.ts.timestamp-1711553549825-4b69edd70157b.mjs":
html-ui:lint: [error] ENOENT: no such file or directory, open '<project_home>/vite-storybook-boilerplate/packages/html-ui/vite.config.ts.timestamp-1711553549825-4b69edd70157b.mjs' Adding the file to ignores is a workaround, but we have to ensure it gets added to each tool... |
File exists due to a bug in `vite` Ref: vitejs/vite#13267
Adding them to .gitignore and using |
Wouldn't it be a better solution to write the generated .mjs to the OS's defined vite/packages/vite/src/node/config.ts Lines 1217 to 1227 in 6cccef7
|
One of our projects is currently struggling with annoying errors caused by these tmp files interfering with Nx and this suggested fix would resolve them, but I am also not knowledgeable enough to judge potential reprecussions. |
I'm getting a similar issue to @OndraSlejtr
|
Workaround that fixed our problem, at least from what we have observed so far, was simple adding wildcard for these tmp files into every ignore possible (.nxignore, .eslintignore, tsconfig and any other tools that might have a problem with these files). |
Unfortunately, as has been mentioned, this does nothing to help in certain environments where the directory isn't writeable. I have containerised my app using docker and the project folder where these files is written is a read-only bind-mount, and even if it wasn't read-only, root permissions would still be required. If I have to allow writes to the host filesystem I start to question the benefit of containerisation in the first place. |
@patak-dev This seems fixed by #13269 but it's still ocurr on the latest version, are you able to fix it correctly? :) |
Can we just change the pattern to use dot files? Instead of: This will solve the vast majority of issues. |
I think it's good idea to avoid creating those files at all. Because ignoring that files isn't solution. Orrr put it inside |
Describe the bug
When I use Ctrl+C to terminate the process of launching vite, I may leave behind the temporary file vite.config.js.timestamp.xxxxx.mjs
By checking the code, I found that the problem may be caused by the loadConfigFromBundledFile method in packages/vite/src/node/config.ts, for esm. When the temporary file is written locally and the process ends, this issue will be triggered, mainly when dynamicImport is time-consuming
I am considering whether it is possible to check and clean up temporary files every time the loadConfigFromBundledFile method is executed
Reproduction
https://stackblitz.com/edit/vitejs-vite-rmx6nh?file=index.html&terminal=dev
Steps to reproduce
No response
System Info
Used Package Manager
pnpm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: