rustywind
CLI for organizing Tailwind CSS classes (by avencera)
Overcommit
A fully configurable and extendable Git hook manager (by sds)
| rustywind | Overcommit | |
|---|---|---|
| 3 | 6 | |
| 466 | 3,906 | |
| 2.6% | - | |
| 8.2 | 6.7 | |
| 8 days ago | about 1 month ago | |
| Rust | Ruby | |
| Apache License 2.0 | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
rustywind
Posts with mentions or reviews of rustywind.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-09-21.
-
Tailwind CSS class sorter – the custom way
RustyWind is a CLI for ordering Tailwind classes but also does not yet support custom regexps.
-
Automatically sorting your Tailwind CSS class names
Enter, Rustywind. It is a CLI rustywind that is installed via npm but written in Rust. I didn't know you could do that either.
-
How do you order class names in the markup?
Yea I think Ima go this route. I just want to be consistent with the organization. I just found https://github.com/avencera/rustywind as well. Its a CLI version of Headwind.
Overcommit
Posts with mentions or reviews of Overcommit.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-06-11.
-
Introduction to Git Hooks
overcommit - A well-maintained, up-to-date, flexible Git hook manager.
-
Linting and Auto-formatting Ruby Code With RuboCop
A great way to ensure that all Ruby code in a project is linted and formatted properly before being checked into source control is by setting up a Git pre-commit hook that runs RuboCop on each staged file. This article will show you how to set it up with Overcommit, a tool for managing and configuring Git pre-commit hooks, but you can also integrate RuboCop with other tools if you already have an existing pre-commit workflow.
-
Tailwind CSS class sorter – the custom way
As a team we want to ensure that everybody commits our templates with classes rightly ordered. We use Overcommit to enforce consistency but any similar tool will do.
-
Run RuboCop on git commit with Overcommit Gem
# Use this file to configure the Overcommit hooks you wish to use. This will # extend the default configuration defined in: # https://github.com/sds/overcommit/blob/master/config/default.yml # # At the topmost level of this YAML file is a key representing type of hook # being run (e.g. pre-commit, commit-msg, etc.). Within each type you can # customize each hook, such as whether to only run it on certain files (via # `include`), whether to only display output if it fails (via `quiet`), etc. # # For a complete list of hooks, see: # https://github.com/sds/overcommit/tree/master/lib/overcommit/hook # # For a complete list of options that you can use to customize hooks, see: # https://github.com/sds/overcommit#configuration # # Uncomment the following lines to make the configuration take effect. PreCommit: RuboCop: enabled: true on_warn: fail # Treat all warnings as failures problem_on_unmodified_line: ignore # run RuboCop only on modified code
-
Automatically sorting your Tailwind CSS class names
Overcommit - run rustywind --write during git commit to update your files before you send them off to git
-
Migrating Tachyons to Tailwind CSS (III – learnings)
By the way, it’s nice that adding (or completely redefining) the scale system is so easy in Tailwind. On the other hand, care must be taken that modifying the defaults is not overused. In the end, we added an Overcommit rule banning further updates of the Tailwind configuration (of course, this can be temporarily disabled, when truly needed).
What are some alternatives?
When comparing rustywind and Overcommit you can also consider the following projects:
headwind - An opinionated Tailwind CSS class sorter built for Visual Studio Code
git-up - NOT MAINTAINED
tailwind-config-viewer - A local UI tool for visualizing your Tailwind CSS configuration file.
Rugged - ruby bindings to libgit2
tailwind-sorter - A ruby gem to sort the Tailwind CSS classes in your templates the custom way.
git-whence - Find the merge and pull request a commit came from + fuzzy search for cherry-picks
crabtyper - A speed typing web app written in Rust
git-auto-bisect - Find the first broken commit without having to learn git bisect
Slim - Slim is a template language whose goal is to reduce the syntax to the essential parts without becoming cryptic.
git-spelunk - git-spelunk, an interactive git history tool
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.
pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.