Next-js-Boilerplate VS tailwindcss-jit

I've built a starter in Nextjs 14 with auth: https://github.com/ixartz/Next-js-Boilerplate

After 3 years of maintaining Next.js Boilerplate, my free and open source Next.js Boilerplate has finally reached more than 5000+ ⭐ stars on GitHub. During these 3 years, I have received countless feedback and contribution to improve the boilerplate. I'm extremely happy, now the template includes:

🌟 Next.js Boilerplate GitHub Repository: Next.js Boilerplate

I am thrilled to announce that Next.js Boilerplate has recently crossed a significant milestone on GitHub. We've reached an impressive 4000 stars! 🚀🎉

For your information, I'm also the author of Next.js Boilerplate, soon reaching 4000 ⭐ on GitHub. And, I hope the React Native Boilerplate can also reached the same number of stars 😀

Thank you Vercel team, it works perfectly! Just updated my Next.js Boilerpalte to version 13.3 without any issue: https://github.com/ixartz/Next-js-Boilerplate

I suppose yes: https://github.com/ixartz/Next-js-Boilerplate/issues/10, several people asked me about integrating storybook

You can find the repository on GitHub at ixartz/Next-js-Boilerplate or you can also check the live demo of Next.js Boilerplate.

I found this GitHub issue where someone wants to use CSS variables for padding, like so: p-[var(--app-padding)]

Just cruised the JIT docs & code on GitHub (merged into main branch).

> add non-default variations (mostly different heights/widths than what it ships with).

Check out https://github.com/tailwindlabs/tailwindcss-jit. It got released 3 weeks ago, and supports variable variables in width and height now.

About two weeks ago, Adam Wathan announced a new Tailwind experiment: Just-In-Time. In this article, I'll tell you what it's all about, and how you can take advantage of it.

In the latest Storybook update, we finally got support for PostCSS 8. So, to celebrate this occasion, I've put together a React Storybook environment that includes everyone's favourite utility-first CSS framework: TailwindCSS. The environment also utilizes the TailwindCSS JIT compiler & Webpack 5 to bring the build times as close to instant as possible. And to top it off, the repo includes a simple GitHub action that deploys the Storybook to GitHub pages every time something is pushed.

Tailwind CSS 2.0 with the Just-in-time version

It’s not a setup issue. The JIT works differently: there’s no “purging”. And the issue I described is a known problem: https://github.com/tailwindlabs/tailwindcss-jit/issues/71

Sidestepping the broader conversation, this "JIT tool" is apparently a postcss plugin, which means you have to spawn postcss process (e.g. at every save events or have build tool do the same).

Enter @tailwindcss/jit, a drop-in replacement (though not with 100% feature parity yet) that collects the classes used by your files and only generates the requested classes.