Discussed in #20382
Originally posted by akomm August 4, 2026
Context: vite/vite-plugin.
Why would you tell, that .gitignore is supported, yet its not really supported as certain notations, like white-listing and wildecard-blacklisting are not understood.
I assume the issue actually silently started with oxide v4, but for some time, it appears, node_modules were generally ignored by default. With some of the updates between 4.1.14 and 4.3.3 this last guard has been removed, blowing up the performance - hmr times of 5-10 seconds, vs. previously ~100ms.
What is funny, trying to debug the issue with DEBUG=* foot-guned the dev server in an infinite loop, as the logs created by tailwind were not excluded (git-ignored though) and it lead to an infinite write-log-reload-write-load cycle that quickly created hundreds of megabytes logs within seconds, clicking which accidentally also crashed vscode.
I guess I will fall back to using @source, but I really struggle to understand why using a format you don't correctly support. Many people probably unnecessary believe everything is fine, but endure worse performance than needed, but not terrible enough like in my case, to realize that it could be much better.
Discussed in #20382
Originally posted by akomm August 4, 2026
Context: vite/vite-plugin.
Why would you tell, that .gitignore is supported, yet its not really supported as certain notations, like white-listing and wildecard-blacklisting are not understood.
I assume the issue actually silently started with oxide v4, but for some time, it appears, node_modules were generally ignored by default. With some of the updates between 4.1.14 and 4.3.3 this last guard has been removed, blowing up the performance - hmr times of 5-10 seconds, vs. previously ~100ms.
What is funny, trying to debug the issue with DEBUG=* foot-guned the dev server in an infinite loop, as the logs created by tailwind were not excluded (git-ignored though) and it lead to an infinite write-log-reload-write-load cycle that quickly created hundreds of megabytes logs within seconds, clicking which accidentally also crashed vscode.
I guess I will fall back to using
@source, but I really struggle to understand why using a format you don't correctly support. Many people probably unnecessary believe everything is fine, but endure worse performance than needed, but not terrible enough like in my case, to realize that it could be much better.