HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
tailwindlabs
tailwindcss
TypeScript2019–2026
tailwindlabs / tailwindcss

tailwindcss

A utility-first CSS framework for rapid UI development.

37Distinct people
39Mentions
1Explicit recommenders
98.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A utility-first CSS framework for rapid UI development.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I love how easy it is to add a PWA selector: https://github.com/tailwindlabs/tailwindcss/discussions/6755

philip1209 used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:56:55 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year39 dated mentions

Observed mentions: 2019-02-26 18:33:35 UTC to 2026-09-15 14:36:52 UTC.

02468102019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 3 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 8 mentions; 4 submissions, 4 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC330
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC844
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC927
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC303
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC505
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC707

What Hacker News says

3 sources
One example is rotation along axes other than Z, which is required for 3D transforms. Here's a two year old issue on it: https://github.com/tailwindlabs/tailwindcss/discussions/3521 Another is attribute selector support. They have many common ones, but to do anything more complex you need to add support to your configuration. https://tailwindcss.com/docs/hover-focus-and-other-states#at... I don't want to oversell this; I think Tailwind does a pretty good job covering the "happy path", and if you haven't run into any gaps I wouldn't worry about it too much. But you'll encounter its limits well before you encounter the limits of CSS.
In Tailwind and the death of web craftsmanship
Prettier also came to mind, and I'm usually pretty happy with the "it's formatted this way, deal with it" approach - but I also would like the tool to behave predictably with updates. Prettier had some changes in 2.5 related to multi-line-classes (namely, forbidding them), which in turn made it unusable for projects with tailwind usage, as it now forces extremely long lines in some cases. (Especially for elements that have styling based on multiple breakpoints and a darkmode variant, you're hitting >120 chars easily). I know that you can go for descriptive classnames and "@apply", but I was still miffed about a change like this in an already existing tool, with a lot of community pushback and no compromise in sight. (Here's a relevant discussion, but keep in mind that multi-line-classes worked at some point and now just don't: https://git
Read the rest
hub.com/tailwindlabs/tailwindcss/discussions/7763) So for prettier, it wasn't just "format your code our way or else" - which is a good approach for a formatter, see also gofmt - it was "your current set up doesn't work anymore, tough luck".
In ProtonMail Rewrites Your Emails

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.