addVitePlugin usage blocks Vite HMR fully

[TechAkayy]

addVitePlugin usage blocks Vite HMR fully

[TechAkayy]

After a lot of trial and error, I have figured out where the issue is:

Nuxt's HMR is getting blocked when, in the custom vite plugin's "config" hook, either the original config object (after mutating it) or a mergedConfig is returned. Vite docs seems to support this return in the config hook.

This HMR break is specific to Nuxt, as HMR is not blocked in a plain Vue project with the same custom vite plugin .

This breaks Nuxt's HMR (returns a merged config)

And after some very long timeout (couple of minutes), this gets logged

This doesn't break HMR (avoids mergeConfig and directly mutates the config)

I have updated my Vite plugin to directly mutate instead returning a config using mergeConfig vite utility. The above is just an example, I do make few other config updates, hence used mergeConfig.

Even though this is solved at my end, why Nuxt's HMR is blocked when using mergeConfig utility and returning a merged config is still a mystery, unless Im not supposed to do this way.

Maintainers, please feel free to close this if you see no action on this issue. Thanks for looking into this.

[TechAkayy]

Updated reproduction to latest (3.13.0) using npx nuxi upgrade --force, and removed vue & vue-router from package.json as they not required to be added explicitly anymore. HMR works nicely 😃 !

Issue doesn't seem to reoccur anymore. Thanks @pi0 @danielroe.