fix(variant-group): hmr in vite

[Simon-He95]

close: #3518

[netlify]

✅ Deploy Preview for unocss ready!

Name	Link
🔨 Latest commit	092a62f
🔍 Latest deploy log	https://app.netlify.com/sites/unocss/deploys/66429f2b1d668700088a153b
😎 Deploy Preview	https://deploy-preview-3741--unocss.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[antfu]

I am not sure about it - can you explain a bit more about the problem and why this would be helpful?

[Simon-He95]

I am not sure about it - can you explain a bit more about the problem and why this would be helpful?
The affectedModules themselves collect all the ids that need to be updated, but our HMR needs to filter these ids based on the clientImportedModules that depend on them, which should enable on-demand updates

[Simon-He95]

Morning, @antfu
I have a question, should we only hot update the current file, or the current file and its sub-files? If it is the current file, there is no need to add ctx.affectedModules.add(id) to the transformerVariantGroup. If necessary, it should Filter all changed pages based on dependencies on the current page

[Simon-He95]

I feel that there is no need to add ctx.affectedModules.add(id) in transformerVariantGroup, because if you modify the hasChanged file, this plug-in will be used. If you do not modify the hasChanged file, it will also trigger the style update of uno.css.

[Simon-He95]

It seems that this line of code is not needed. It will cause additional updates. For example, I modified file a, but multiple files may be added to the change list for the first time. Modification of file a will cause hot updates of all files. uno.css is also updated multiple times. If the a file changes, you should only need to initiate the hot update of the a file and the hot update of uno.css.

[antfu]

I am still not convinced - but I am ok have it and to experiments a bit