tailwindcss-jit VS prettier

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.

Prettier: An opinionated code formatter that enforces a consistent code style.

Automating code checks with static code analysis allows us to enforce code styling effectively. By integrating tools into our workflow, we can identify errors at an early stage, while coding instead of blocking us at the end. For instance, flake8 checks Python code for style and errors, eslint performs similar checks for JavaScript, and prettier automatically formats code to maintain consistency.

So anyways, I wanted to hook up Emacs with Astro support. For now, I've just been roughing it out there and running Prettier by itself and turning off save on format and auto-complete. It's been scary.

If you're a developer, you're surely familiar with Prettier and ESLint. With over 8 years of existence, they have established themselves as references in the JavaScript ecosystem.

prettier is used to format you text

No formatting inconsistencies: The committed code should follow the organization's code formatting standards(prettier or pretty-quick).

Let’s walk through the steps for a one-time setup to configure husky pre-commit and pre-push hooks, ESLint with code styles conventions, prettier code formatter, and lint-staged. Husky automatically runs a script on each commit or push. This is useful for linting files to enforce code styles that keeps the entire code base following conventions.

GitHub | Website

Prettier: An opinionated code formatter that enforces a consistent code style.

What is Prettier 😎?