-
Notifications
You must be signed in to change notification settings - Fork 22
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
Frequent Vite Optimize Info errors #1039
Comments
An alternative solution for #974 that I have found is manually renaming I've also seen some mention online that it could be some sort of read-only/permission issue with |
Heh I was so happy this was fixed, pulled too early. 👮 https://github.com/ramp4-pcar4/ramp4-pcar4/actions/runs/2509693813 Am seeing the same thing when doing the command locally. Update: local build finished in about 20 mins. Github hosted one takes around an hour. |
I'll keep an eye out for when this gets fixed by the Vite folks. |
Problem on our end fixed for now by #1159 |
Have not encountered in a few months. Well done. |
Related to #974
The issue above provides a working fix. But this problem happens all the time, not just when updating dependencies. It's also happening with a good number of team members. Frequently watching your dev build die, then having to clear out caches and do it over adds up when it comes to wasted time.
Would like to see a preventative solution found instead the fix-after-it-breaks path we currently have.
Maybe the
npm run dev
can run some sort of pre-clean? Alternately a search around the internet could reveal better solutions (I'd guess killing the cache before each run has some efficiency detriment when things don't mess up).The text was updated successfully, but these errors were encountered: