Select Page

Category: linting

In Search of a Stack That Monitors the Quality and Complexity of CSS

Many developers write about how to maintain a CSS codebase, yet not a lot of them write about how they measure the quality of that codebase. Sure, we have excellent linters like StyleLint and CSSLint, but they only help at preventing mistakes at a micro level. Using a wrong color notation, adding a vendor prefix when you’re already using Autoprefixer, writing a selector in an inconsistent way… that kind of thing. We’re constantly looking for ways to improve the way we write CSS: OOCSS, BEM, SMACSS, ITCSS, utility-first and more. But where other development communities seem to have progressed...

Read More

Prettier + Stylelint: Writing Very Clean CSS (Or, Keeping Clean Code is a Two-Tool Game)

It sure is nice having a whole codebase that is perfectly compliant to a set of code style guidelines. All the files use the same indentation, the same quote style, the same spacing and line-break rules, heck, tiny things like the way zero’s in values are handled and how keyframes are named. It seems like a tall order, but these days, it’s easier than ever. It seems to me it’s become a two-tool game: A tool to automatically fix easy-to-fix problems A tool to warn about harder-to-fix problems Half the battle: Prettier Otherwise known as “fix things for me,...

Read More