4 ms·

I tried JIT mode, loved its features like arbitrary styles, but eventually I switched back to default tailwind config. So, when you use JIT you no longer get a

I tried JIT mode, loved its features like arbitrary styles, but eventually I switched back to default tailwind config. So, when you use JIT you no longer get all tailwind classes in chrome dev tools only the ones you applied to components. I know it's by design to keep css lightweight. But that also means I can no longer design UI using Chrome dev tools. Only when I apply tw classes directly to component in editor like vscode it reflects the change in browser. this back and forth cycle between editor and chrome took the fun away from me :(

colinclerk 6y ago
This is what inspired me to look into true JIT: https://news.ycombinator.com/item?id=26731816 https://news.ycombinator.com/item?id=26731816
- raihansaputra 6y ago
  Somebody already wrote a library for client-side JIT TailwindCSS. and tbh I really want this taken to the extreme and see how much is the overhead compared to shipping + parsing CSS. https://github.com/matyunya/headlong https://github.com/matyunya/headlong