..., CSS Modules, CSS-in-JS, and Tailwind when I'm not constrained to do so. - Source: dev.to / 6 months ago

From what I read about CSS modules, the style isolation provides some guard rails to prevent things like random bits of global style or having colliding rules all over the place. This makes a lot of sense, but even on huge projects, I never really have those problems. I've disciplined myself to pair a component file with a CSS file (MyComponent.jsx + MyComponent.css) and keep global styles to a minimum. Source: about 2 years ago

Any time you import CSS files into a module, that CSS becomes active on EVERY component in your entire project, so that's not really a good way to go about it. It essentially creates a tag inside the final rendered html with all of your CSS within it. If you have two CSS files, and they both have a class of .myClass then they will step on each other and cause bad things to happen to your... Source: over 2 years ago

They are probably using css modules. Source: over 2 years ago

This may be a little more advanced but I'd also recommend looking into CSS modules. It basically allows you to scope your styles to individual elements preventing unwanted cascading, and simplifies naming conventions a lot (since the class names are now variables). Source: over 2 years ago

Unlike other frameworks, you can’t just npm install and write code. Take one look at the Tailwind CSS installation page and before you even begin, you need to decide if you want to install it with the CLI or as a PostCSS plugin. Wait, you know CSS, but what is PostCSS? Then, you keep reading and you see something about CSS preprocessor and you might wonder what that is too. Then, you see that you not only have to... - Source: dev.to / about 1 year ago

Mixins - This allows you to reuse a set of rules inside another rule. I never really found a good use case for mixins. They were available to me when I was still using Bootstrap with LESS, but using them seemed a little complex, because you always need to look up what they do and the resulting CSS output is not always clear. If you're thinking of using them for browser prefixes (e.g. -webkit-transform), I would... - Source: dev.to / over 1 year ago

Simple, fast, and a little bit opinionated, Eleventy Plus Vite features Eleventy 2.0.0-canary, the new Eleventy 2.0 Dev Server with live reload, Vite 3.0 as Middleware in Eleventy Dev Server (using eleventy-plugin-vite), build output post-processing by Vite (with Rollup), CSS/Sass post-processing with PostCSS including Autoprefixer and cssnano, a custom CSS/Sass structure, basic fluid typography based on Utopia,... - Source: dev.to / over 2 years ago

w/ postcss-preset-env(v7.8.3): convert modern CSS into something most browsers can understand, determining the polyfills you need based on your targeted browsers or runtime environments. It takes the support data that comes from MDN and Can I Use and determine from a browserlist whether those transformations are needed. It also packs Autoprefixer within and shares the list with it, so prefixes are only applied... - Source: dev.to / over 2 years ago

As others have said, you need to normalize. Also, you may need something like autoprefixer if you're using styles that have different vendor prefixes. https://github.com/postcss/autoprefixer. Source: over 2 years ago