isn't it postcss/purgecss doing this on tailwind's behalf? this process also strips styles that are not in the actual html/template files being scanned and are

isn't it postcss/purgecss doing this on tailwind's behalf? this process also strips styles that are not in the actual html/template files being scanned and are only shown in error paths or in some other way. it also strips styles applied directly to tags (without class). i find it quite messy to maintain purge ignore lists and making extra-extra sure that the removal regexp is correct as it can remove valid classes added/removed by templating libraries like jinja. proper css coverage is more than a glorified grep that looks for all the tailwind class names...