rem’s avatarrem’s Twitter Archive—№ 73,682

  1. I really don't understand css modules. I thought that I could "just" use the first top level element and the cascade in my comp.module.css would work. But no, it seems like I need to mirror the JS style prop against everywhere that I'd put a class…surely I've got this wrong?
    On twitter.com Twitter logo rem’s avatar ❤️ 5 Favorites Mood +1 🙂
    1. …in reply to @rem
      Perhaps that problem is that I don't do CSS At Scale (quite note: the vast majority of devs aren't doing anything At Scale that these problems are supposed to solve), I just kind of want to import my CSS and it's scoped, and the cascade works and I don't need config.
      Permalink On twitter.com Twitter logo rem’s avatar ❤️ 1 Favorite Mood 0
      1. …in reply to @rem
        Oh…so, this isn't really CSS then? I'm confused as to what CSS modules really is - I'm absolutely certain this can't be it.
        oh my god twitter doesn’t include alt text from images in their API
        Permalink On twitter.com Twitter logo rem’s avatar ❤️ 7 Favorites Mood -1 🙁
        1. …in reply to @rem
          So *this* is exactly the issue I've run into: github.com/vercel/next.js/issues/10475 I'm using nested css to avoid "class collisions" (which css modules purport to solve) - which to me seems pretty sensible, and yet css modules, specifically(?) doesn't let me use postcss nesting…
          Permalink On twitter.com Twitter logo rem’s avatar ❤️ 1 Favorite Mood -1 🙁
          1. …in reply to @rem
            This morning is sponsored by confusion and frustration. They paid equally for my attention today.
            Permalink On twitter.com Twitter logo rem’s avatar ❤️ 3 Favorites Mood -2 🙁