[HN Gopher] Tailwind CSS v2.2
       ___________________________________________________________________
        
       Tailwind CSS v2.2
        
       Author : joshmanders
       Score  : 23 points
       Date   : 2021-06-17 16:19 UTC (6 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | atonse wrote:
       | Our build times for our ember JS app went from 60 seconds to
       | something like 7-8 minutes since including tailwind. And
       | TailwindJIT introduced some odd bugs where we had to leave it
       | off. So far it's made the dev harder in some ways that have
       | nothing to do with all the actual CSS benefits we realized. We'll
       | try 2.2 to see if it helps.
       | 
       | I am really hoping someone is working on a go or rust version of
       | the tailwind compiler, and we'll see those speeds come down from
       | multiple minutes down to 800ms and see just how utterly silly JS
       | tooling performance is.
        
         | adamwathan wrote:
         | Hey! Sorry to hear about this -- the core of the problem you're
         | facing I expect is that build tooling struggles very much with
         | large CSS files, so no matter how fast you can generate the
         | CSS, if it's like 8mb because you have a rich config file and
         | you're in development so you're not purging, the overall build
         | is going to be slow. We've tested this a bunch by feeding
         | static CSS files of this size into webpack without having
         | Tailwind in the build process at all.
         | 
         | The JIT engine is our solution to this, and ensures the CSS
         | file is never large so it never causes these issues. We have
         | done a ton of work to iron out bugs in the new engine between
         | 2.1 and 2.2 so I would definitely give it a shot and see how it
         | goes.
         | 
         | Consider even using our new CLI tool to compile your CSS
         | instead of integrating it into your Ember build step -- on the
         | biggest project we've tried (over 400 template files, some
         | thousands of lines long), the new CLI compiles the CSS in about
         | 400ms, and incremental rebuilds when you save a template file
         | take 3-10ms.
        
         | kactus wrote:
         | Tailwind JIT is really fast, drastically cut my build times
         | down. I don't like how slow JS tooling can be either. The JIT
         | compiler makes a big difference.
        
         | thomaslord wrote:
         | What kind of bugs have you seen? I haven't tried Tailwind JIT
         | yet but I'm hoping to eventually switch over a work project and
         | I'd love to have some idea of when I'm getting myself into.
        
         | seumars wrote:
         | What made you switch to tailwind in the first place?
        
       | commotionfever wrote:
       | nice video running though all the features:
       | https://www.youtube.com/watch?v=DxcJbrs6rKk
        
       ___________________________________________________________________
       (page generated 2021-06-17 23:02 UTC)