Use ViteRestart to detect config changes

[streino]

Solution for #846 (comment)

Turns out we were not even restarting on base config...

[JeSuisUnCaillou]

This is still a draft, should we wait to review ?

[JeSuisUnCaillou]

Turns out we were not even restarting on base config...

I'm 84% sure I tried on the main branch to change a config and the hot reload was watching it. Let me retry... Yeah, I confirm that modifying the config on the main doesn't require a restart of the dev server to be taking into account.

(I'll look into your solution anyway 😉 )

[JeSuisUnCaillou]

Seems legit to me 👍

We can merge this into #846 then into #828, and I'll work on the rebase then.

[streino]

This is still a draft, should we wait to review ?

It's really just a proposal so I figured "draft" was appropriate. Feel free to pull it into your PR if you find it useful.

Turns out we were not even restarting on base config...

I'm 84% sure I tried on the main branch to change a config and the hot reload was watching it. Let me retry... Yeah, I confirm that modifying the config on the main doesn't require a restart of the dev server to be taking into account.

Right... Works for me as well. I used the wrong branch to test :/
We likely broke auto-reload by replacing the file config with a string, meaning there's no more import config from '@siteConfig/config.yaml' that knows when to trigger a reload.