Hello,

I had been wondering about the Vite console message saying, "Re-optimizing dependencies because Vite config has changed," which I often saw while developing Waku. As it turns out, because Waku uses more than one Vite process, there are race conditions that make dependency pre-bundling obsolete. We had to clear the .vite cache folder to run apps stably in development mode. Today, I looked into the Vite source code to understand how Vite detects config changes. It calculates a hash from some properties of the config object. To overcome the situation with two Vite processes, I implemented a little hack so that the hash values become identical for both processes. Whoa! It works. Now I can sleep well. My concern is that if Vite changes its hash calculation logic, we'll need to adapt to it.

We'll be releasing Waku v0.19.0 soon!

Happy Hacking.

0 comments

HackDiary#111

HackDiary#110

HackDiary#109

HackDiary#108

HackDiary#107

See all posts from Daishi Kato