@ddubb3000
Loving this Vite course really get you up to speed quickly!
@krzysztofkrawczynski9404
I love this approach. Remember to keep your socs clean 😄 (Separation of Concerns, not laundry… though that too). I’ve found this method especially useful when vibe coding. With React + Tailwind, I always had to double-check if the AI hadn’t accidentally replaced some logic. With CSS Modules, that’s no longer an issue.
@AVidhanR
I never knew this. Thanks!
@drissfarji
It’s great to see the excitement around CSS Modules with Vite, but it’s worth pointing out that Angular has had this kind of built-in style encapsulation since version 2 (back in 2016). In Angular, each component can have its own scoped styles using regular CSS files — no need for .module.css files or class imports. The framework handles style scoping natively through ViewEncapsulation, automatically preventing global conflicts without extra configuration. It’s a long-standing feature that often gets overlooked outside the Angular community.
@bluosu
100% thought he was talking about cs:go
@QuickLit-0401
I'm scared i don't understand any of this 😢
@jimcab1853
Mahdi?
@ericritter46
Hes gotta rob a train coach after this special 😅
@cenkakay3506
heil tailwind
@NeverLuckyEngineering
Careful with that hankie the pinkertons will get you
@sajadmalik9097
I hate this Module css files… I have not much experience with these except for working couple of months using these modules and I hated it… it looks your html syntax look so ugly that you feel like wth..
@phatcharaphonpromjom2317
How can we use this concept against 3rd-party scripts like consent, chat popups that load the exact same css classes with our own css (especially tailwind), its messed up so bad 🫨
@Jason-ot6jv