ReliCSS | CSS-Tips

All of us have a number of skeletons in our CSS closets. There’s most likely that one-off !vital the place now you can handle that extra successfully with cascade layers. Or possibly a dated Checkbox Hack that :has() has solved. Maybe it’s been an extended whereas since your final website redesign and it’s chock-full of vendor-prefixed properties from 2012. Thar be demons!

Stu Robson’s ReliCSS (intelligent identify!) instrument can excavate outdated CSS in your codebase which have trendy CSS options.

Every relic is assigned a stage of severity. As Stu explains it:

• Excessive Severity: True “fossils”. Hacks for (now) unsupported browsers (IE6/7) or “harmful” strategies. Excessive-risk, out of date, needs to be first targets for removing.
• Medium Severity: The center floor. Hacks for older unsupported browsers (IE8-10). They work however they’re fragile. Hacks to overview to see in the event that they’re nonetheless related in your precise customers.
• Low Severity: Trendy artifacts. Often vendor prefixes (-webkit-, -moz-). Secure principally, however higher dealt with by automated instruments like Autoprefixer. They’re a possibility to enhance your construct course of.

It’s been a short while since my private website received an overhaul. To not toot my very own horn, however heyyyyyy!

Critically, although. I do know there are issues in there I’m embarrassed to confess.

However what if we do archeological dig on CSS-Tips? I imply, it’s been at least 5 years since this place has gotten the adore it deserves. I’m nearly afraid to look. Right here goes…

OK, not as unhealthy as I imagined. It’s largely vendor prefixing, which I’m certain comes courtesy of an older Autoprefixer configuration.

Direct Hyperlink →