Open alexandertrefz opened 2 years ago
Thanks for letting me know. This seems to be the similar problem mentioned in #19: the way the Tailwind processes variants does not work with nested selectors currently used in my implementation. Perhaps dynamic tracking adjustment wasn't a good idea, I don't see any practical causes to use it. So, probably I should remove it and keep applying dynamic metrics to the default (base) values only? This could potentially fix both this issue and #19.
Unfortunately, due to the lack of time, it's going to be slow on finding some best solution, sorry. So, any suggestions or help will be appreciated.
I have set up a barebones Setup with Vue and Vite, where purging generally does work. I have double checked by removing utility classes, and I do get the warning that none are detected when I remove all, and I do see the file-sizes fluctuate as expected. Using this great (seriously!) plugin however, as soon as I use
.font-inter
the CSS size jumps up by about 20kb uncompressed.This seems to be caused by the various
.tracking-*
classes that get output in all their great variety, even though i dont use them, or the.text-*
classes at all.Granted, since there is so much repetition, broetli happily reduces the compressed difference to just 2kb, but it might be something to look into, regardless.