A few releases have gone out since the initial announcement — v0.1.3 is the latest. Changelog: Changelog — canonical_tailwind v0.3.0
aptinio
aptinio
Just shipped 0.1.5. The headline: if format-on-save just wasn’t working for you under Expert or ElixirLS, 0.1.5 fixes it.
Also tightened pool reliability: workers that go missing now recover (long-running LSP sessions used to break after a crash), cold start is serialized to avoid mixed-config workers, and config drift after pool start raises a loud error instead of silently using stale config (a small breaking change for umbrella setups that depended on the old quiet behavior).
And if you haven’t tried canonical_tailwind yet, this is a good moment. The canonicalizer in tailwindcss has gotten noticeably smarter over the past few releases: combining text-* with leading-*, collapsing matching width/height into size-*, modernizing calc(var(--spacing)*…) into --spacing(…), and now in v4.3.0, migrating [&:has(…)] to has-[…] and preserving significant whitespace and original units in arbitrary values. canonical_tailwind delegates to the user’s installed binary, so all of that lands for you the moment you bump :tailwind.
Changelog: Changelog — canonical_tailwind v0.3.0
Hope you find it useful!
4
johns10davenport
aptinio
Just shipped 0.2.0. It’s faster.
It used to run a pool of tailwindcss CLI processes to parallelize mix format. But that pool only ever helped a full-tree format. Since Elixir 1.17, mix format caches unchanged files, so even that only runs over the whole tree on the first format or a fresh CI checkout. Everything else (format-on-save, a single file, a repeat mix format after edits) touches a handful of files, which one warm CLI handles fine. 0.2.0 drops the pool for that single warm CLI, so those everyday cases start sooner. The one tradeoff is the first full-tree format, which gives up the old parallelism.
It’s also lighter: a long editor session now holds one CLI instead of up to six, so a few hundred MB instead of well over a gigabyte.
And the single CLI is now keyed per resolved configuration, so one mix format can span apps or directories that resolve to different configs: an umbrella with per-app tailwind profiles, or a project using subdirectories with per-directory .formatter.exs files. Each config gets its own warm CLI.
If you’re upgrading: :pool_size is deprecated and ignored, and the config-drift error from 0.1.5 is gone, so the per-app workaround for mismatched umbrella configs is no longer needed.
Changelog: Release v0.2.0 · aptinio/canonical_tailwind · GitHub
Hope you find it useful!
2
aptinio
Just shipped 0.3.0. There’s a new ~TW sigil.
canonical_tailwind already canonicalizes class attributes in HEEx. But Tailwind classes often live in plain .ex code too: helper functions, module attributes, class-builder lists. A formatter can’t safely touch those on its own, since it can’t tell a Tailwind class string from any other string.
~TW lets you mark a string as a class list, so mix format canonicalizes it:
defp button_class, do: ~TW"px-4 py-2 inline-flex rounded-md bg-brand"
# becomes, on mix format:
defp button_class, do: ~TW"inline-flex rounded-md bg-brand px-4 py-2"
It works anywhere a string literal does. It’s opt-in per string, so you canonicalize the strings you want and leave the lists you’ve ordered by hand.
Add CanonicalTailwind to your formatter :plugins and import CanonicalTailwind.Sigil to use it.
Hope you find it useful!
4