truss
| class-types.macro | truss | |
|---|---|---|
| 3 | 5 | |
| 7 | 31 | |
| - | - | |
| 0.0 | 6.3 | |
| over 1 year ago | about 2 months ago | |
| TypeScript | TypeScript | |
| MIT License | - |
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.
class-types.macro
- TailwindCSS JIT with Arbitrary Values
-
I Don't Like Tailwind CSS
The only thing I really didn't like about tailwind was the danger of changing tailwind.config and the long className lists. I "solved" both of those issues with a simple macro and PostCSS plugin: https://github.com/fleck/class-types.macro#why-use-this-libr...
truss
-
StyleX – Meta's Styling Library
Nice! We copied StyleX's "type-safe extensions" in Truss [1] so things like `` are allowed (setting margin is fine) while disallowing `` (anything "not margin") that would mess up the components internal impl details with a compile error.
That said, we don't actually use the feature that much, vs. higher-level logical props like ``.
I know we're supposed to use build-time CSS-in-JS these days, but afaiu they don't support the rare-but-handy "just spread together ~4-5 different object literals from ~random different conditionals + props", i.e. intermixing styles some inside the component + outside the component, which emotion handles really well.
Basically this [2]. StyleX says it does "cross-file styles"...but can it support that? I kinda assume not, but I'm not sure.
[1]: https://github.com/homebound-team/truss#xstyles--xss-extensi...
[2]: https://github.com/homebound-team/beam/blob/main/src/compone...
-
What working with Tailwind CSS every day for 2 years looks like
Fwiw to the avoid 80%-in-TW / 20%-in-SCSS-or-something-else dichotomy/complexity, we built Truss which brings TW (Tachyons) style abbreviations to the existing "something else" tool chain (Emotion in our case).
So then everything goes through a single system.
https://github.com/homebound-team/truss
> tailwind's and SCSS's VS code integration is pretty amazing
We get that too, by being just vanilla TypeScript, no editor-specific integration necessary. :-D
(I've linked to Truss in another response, so will stop now. :-))
- Why Tailwindcss over styled-components?
- Ask HN: Who is hiring? (November 2021)
-
TailwindCSS JIT with Arbitrary Values
Don't want to take away from Tailwind, it's great.
That said, self-promotion disclaimer but if you like inline/utility CSS, and also like TypeScript/React/Emotion, we've got a "Tailwinds-ish" CSS-in-JS library that we've enjoyed so far:
https://github.com/homebound-team/truss
What are some alternatives?
eslint-plugin-tailwind - ESLint rules for Tailwind CSS
docker-node-example - An example Node / Express app that's using Docker and Docker Compose.
styled-jsx - Full CSS support for JSX without compromises
headwind - An opinionated Tailwind CSS class sorter built for Visual Studio Code
tailblocks - Ready-to-use Tailwind CSS blocks.
beam - 🪵 Beam Design System
headlong - Tailwind CSS on the fly without PostCSS
TimescaleDB - An open-source time-series SQL database optimized for fast ingest and complex queries. Packaged as a PostgreSQL extension.
docker-django-example - A production ready example Django app that's using Docker and Docker Compose.
docker-flask-example - A production ready example Flask app that's using Docker and Docker Compose.