Re:PurifyCSS – Remove unused CSS
by Zikes on Friday June 12, 2015 @03:21PM
(#9707999)
I honestly think this needs to be a part of Chrome Dev Tools's profiler. Already it's able to record sessions that persist across page loads, and tracks what CSS selectors are applied and which properties are overridden. I don't think it's much of a stretch to add a feature like this.
[ Parent
| on HN ]
+1 for something along these lines to be available in all vendor's dev tools!
Re:PurifyCSS – Remove unused CSS
by WhiteNoiz3 on Friday June 12, 2015 @03:38PM
(#9708088)
Agreed! We need something that collects data from multiple pages as you browse through and use your site. At the end it gives you a table of all your classes that didn't match anything (with line number references to your css file).
Re:PurifyCSS – Remove unused CSS
by Existenceblinks on Friday June 12, 2015 @09:14PM
(#9709471)
Though you need to manually visit all those pages. And it wouldn't be easy to traverse DOM with those server side logic/condition.
IMHO, do it offline and out of browser would be easier. But I also think doing it directly with the codes can be hard too since there are so many way that those css will be added to templates.
Re:PurifyCSS – Remove unused CSS
by LoSboccacc on Saturday June 13, 2015 @01:08AM
(#9709967)
Unless the pages are dynamically generated