prettier-plugin-tailwindcss
compiled
prettier-plugin-tailwindcss | compiled | |
---|---|---|
15 | 16 | |
4,779 | 1,962 | |
3.3% | 0.4% | |
8.2 | 9.0 | |
20 days ago | 6 days ago | |
JavaScript | TypeScript | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
prettier-plugin-tailwindcss
-
Tailwind CSS for frontend teams: From settings to rules
Since this was a problem that many people had already encountered, there was already a solution. The first thing I found was Tailwind's official Prettier plugin, which ensures that class names are always ordered according to a certain rule. Best of all, it's auto-correcting, so I don't accidentally miss something or commit a different order.
-
Use TailwindCSS prefixes for shared design system components
It's not as if the correct order for the rules is mysterious. It's implemented in the Tailwind compiler. Tools like prettier-plugin-tailwindcss, which automatically sorts the class names in your HTML code to match the order in which Tailwind generates them in your CSS output, use a public API in Tailwind to get this order.
-
Tailwind CSS Tips and Tricks Worth Knowing
Other than that, you can get Prettier sorting your classes with the Tailwind Prettier plugin. And one more quality-of-life extension that might help your eye sores from a long list of classes is Tailwind Fold.
- Automatic Class Sorting with Tailwind and Prettier
-
How do you get the tailwindcss prettier plugin to work in electron-react-boilerplate?
I everyone. I am using Electron react boilerplate and I have successfully added tailwindcss to the project. However, I am struggling to get the Prettier plugin tailwindcss to work. I’ve tried following the instructions in the readme but no luck. I’ve tried moving my prettier.config.js to the .erc/config dir with no luck either.
-
Why is tailwind so hyped?
Others have already replied, but if you need to structure your TailwindCSS classes, I recommend their official Prettier plugin which integrates well into an ESLint setup.
- I've started breaking tailwind classes into multiple lines and feel like this is much easier to read than having all the classes on one line. Does anyone else do that? Any drawback to it?
-
Tailwind CSS v3.2 – Introducing Container Queries, Multiple Configs and More
> Except that I read that it's great for writing, but a nightmare for reading.
This is true at first. I can see it being pretty daunting to come into an existing project and trying to understand the styling of components. Starting from scratch and easing it into an existing project is much easier imo. That's what I did for a personal website. Now that I understand it and have converted the entire website to Tailwind, I don't want to switch to anything else going forward.
Here's a Prettier plugin that sort the classes to keep everything consistent across components: https://github.com/tailwindlabs/prettier-plugin-tailwindcss
Tailwind combined with classnames (https://github.com/JedWatson/classnames) makes it really easy to have conditional styling based on component state.
-
Fastest Frontend Tools in 2022
Despite the existence of Prettier, arguments about code style such as how to sort ES module imports still exist. Manually sorting ES modules wastes time, and usually leads to losing context when you are writing code and then have to navigate to the top of a file to modify your import statements. I love using the @trivago/prettier-plugin-sort-imports plugin which automatically sorts new imports, and works perfectly together with TypeScript's auto-import feature. Similarly, prettier-plugin-tailwindcss automatically sorts Tailwind classes in your code.
-
HyperUI Rewritten... What's Changed?
Added the tailwind-prettier-plugin as not everyone uses headwind
compiled
-
Why is tailwind so hyped?
tags inside SFCs are typically injected as native
</code> tags during development to support hot updates. <strong>For production they can be extracted and merged into a single CSS file.</strong></p> </blockquote> <p>There are also 3rd party CSS libs that do the same thing such as <a href="https://linaria.dev/">linaria</a>, <a href="https://vanilla-extract.style/">vanilla-extract</a>, and <a href="https://compiledcssinjs.com/">compiled CSS</a>. Which can be used in the event you're stuck with something that doesn't have baked in support via SFC formats (looking at you React).</p> <p>These are my preferred ways of handing it.</p> <ol> <li>Tailwind</li> </ol> <p>Option 2 is tailwind, which works backwards.</p> <p>That is, instead of the above with extraction where you write the styles, and the framework or libs extract them and replace them with class names, it's the other way around.</p> <p>You're writing class names first (which are essentially aggregated CSS property-values) which then generate and/or reference styles.</p> <p>It has the advantage of being easy to write (assuming you've got editor LSP, linting, etc), but as you've discovered, it's difficult to read / can get really messy really fast.</p> <p>As far as all the other claims on the Tailwind site, it's all marketing, at least 80% bullshit.</p> </div>
- Individual css for every component?
-
Hey friendos, need some help choosing a "framework" with some specific requirements in mind
Your choice of CSS lib. Bootstrap can still be a valid choice, tho you may want to check the docs of whatever SSR / SSG framework you end up using as they may have better (or worse support). For example if you wanted to do CSS-in-JS (Next) i'd consider Linaria, vanilla-extract, or compiled.
-
Why We're Breaking Up with CSS-in-JS
So to be extremely clear, the issue isn't CSS-in-JS per se, it's just that the author only looked at implementations that don't generate create CSS files. He notably mentioned the (apparent) zero-runtime solutions Vanilla Extract and Linaria, only to skip them and complain that Compiled inserts nodes at runtime.
Compiled
-
How common is using styled components?
Link: https://compiledcssinjs.com/
-
SASS vs CSS Modules vs CSS-in-JS vs Compile time CSS-in-JS. Who wins?
Compiled (Compile time CSS-in-JS solution from Atlassian)
-
CSS in JS zero runtime libraries similar to JSS which allow to reuse styles?
Stitches Is near zero runtime and vanilla-extract claims it's zero runtime and typed. There's atlassian compiled as well but I never used it.
-
Goodbye CSS Modules, Hello TailwindCSS
Author here, I haven't had time to play around with it, but this library[0] from Atlassian looks like a "best of the both worlds" styling approach: CSS-in-JS authorship without the runtime penalty.
[0] https://compiledcssinjs.com/
- A familiar and performant compile time CSS-in-JS library for React
What are some alternatives?
headwind - An opinionated Tailwind CSS class sorter built for Visual Studio Code
linaria - Zero-runtime CSS in JS library
eslint-plugin-tailwindcss - ESLint plugin for Tailwind CSS usage
identity-obj-proxy - An identity object using ES6 proxies. Useful for mocking webpack imports like CSS Modules.
Visual Studio Code - Visual Studio Code
vanilla-extract - Zero-runtime Stylesheets-in-TypeScript
ESLint - Find and fix problems in your JavaScript code.
twin.macro - 🦹♂️ Twin blends the magic of Tailwind with the flexibility of css-in-js (emotion, styled-components, solid-styled-components, stitches and goober) at build time.
husky - Git hooks made easy 🐶 woof!
stitches - [Not Actively Maintained] CSS-in-JS with near-zero runtime, SSR, multi-variant support, and a best-in-class developer experience.
prettier - Prettier is an opinionated code formatter.
tailwindcss-classnames - Functional typed classnames for TailwindCSS