-
The upstream
tailwindcss
executable has been extracted from this gem into a new dependency,tailwindcss-ruby
. @flavorjonesIn advance of the upcoming TailwindCSS v4 release, we are decoupling the
tailwindcss
executable from the Rails integration. This will allow users to upgrade TailwindCSS at a time of their choosing, and allow early adopters to start using the beta releases.
- Fix the scaffold form template to render text forms and check boxes properly in all versions of Rails. (#418) @Earlopain
- Fix the scaffold form template to render checkboxes properly. (#416) @enderahmetyurt
- Proactively support changes to Rails's authentication templates shipping in Rails 8.0.0.beta2 (which is not yet released). (#407, #408) @seanpdoyle @flavorjones
- Update to Tailwind CSS v3.4.13 @flavorjones
- Update to Tailwind CSS v3.4.12 @flavorjones
- Update to Tailwind CSS v3.4.11 @flavorjones
- Update to Tailwind CSS v3.4.10 @flavorjones
- Update to Tailwind CSS v3.4.9 @flavorjones
- Update to Tailwind CSS v3.4.8 @flavorjones
- Add specialized views for the new authentication generator coming in Rails 8. (#384) @yshmarov @dhh @flavorjones
- During installation, clobber the Rails v8 default
bin/dev
file without requiring human intervention. (#385) @jeromedalbert
- Update to Tailwind CSS v3.4.7 (#383) @flavorjones
- Update to Tailwind CSS v3.4.6 (#381) @flavorjones
- Update to Tailwind CSS v3.4.5 (#380) @flavorjones
- Update to Tailwind CSS v3.4.4 (#373) @flavorjones
- Increase form input field border contrast. (#356) @olivierlacan
- Bring the scaffold templates up to date with rails/rails. (#357, #359) @kinsomicrote
- Drop support for Rails 6.0, which reached end-of-life in June 2023. (#358) @flavorjones
- Drop feature and bug fix support for Rails 6.1. The previous minor release will still receive security support while Rails 6.1 is supported. (#359) @flavorjones
- Remove the
@tailwindcss/aspect-ratio
plugin from thetailwind.config.js
that gets installed by the generator. This plugin was originally a polyfill until Safari 15 was released (in Fall 2021), and so is beyond its useful lifetime for anyone not targetting ancient browsers. (#344) @flavorjones @searls
- Fix debugger repl when using the Puma plugin. (#349) @tompng
- Update to Tailwind CSS v3.4.3 from v3.4.1 by @flavorjones
- The
tailwindcss:watch
task handles interrupts more cleanly. (#318, #336) @davidcelis
- Allow applications to override the generator templates. (#314) @flavorjones
- Support using PostCSS as a preprocessor. (#316) @ahmeij
- Update to Tailwind CSS v3.4.1 from v3.4.0 by @flavorjones
- Fix
password
form field styling in generated scaffold forms. (#304, #307) @flavorjones - Fix namespaced mailer generation. (#272, #308) @flavorjones
- Allow overriding the generator templates by placing application templates in either
lib/templates/tailwindcss/{scaffold,mailer,controller}
orlib/templates/erb/{scaffold,mailer,controller}
. (#164, #314) @flavorjones
- Introduce a Puma plugin to manage the Tailwind "watch" process from
rails server
. (#300) @npezza93 - Lazily load the debugger gem when running
bin/dev
(#292) @elia - Allow choosing a custom port with a
PORT
environment variable when runningbin/dev
(#292) @elia
- Update to Tailwind CSS v3.4.0 from v3.3.6 by @flavorjones
- Update to Tailwind CSS v3.3.6 from v3.3.5 by @flavorjones
- Update to Tailwind CSS v3.3.5 from v3.3.3 by @flavorjones
- Also see v3.3.4 release notes
- Restore support for Ruby 2.7, broken in v2.0.31, by explicitly setting
required_rubygems_version = ">= 3.2.0"
. (#286) by @flavorjones
- Update Procfile.dev to run foreman with
--open
option allowing remote sessions withrdbg --attach
(#281) by @duduribeiro - Address Rubygems 3.5.0 deprecation warnings (#280) by @lylo
- Update to Tailwind CSS v3.3.3 by @flavorjones
- If defined, the
spec:prepare
rake task will be decorated withtailwindcss:build
(#271) by @rmehner
- Update to Tailwind CSS v3.3.2 by @flavorjones
- The
watch
task accepts analways
argument to keep the watcher alive when stdin is closed:rails tailwindcss:watch[always]
. #262 by @GoodForOneFare
- Update to Tailwind CSS v3.3.1 by @flavorjones
- Update to Tailwind CSS v3.3.0 by @tysongach
- Use a locally-installed
tailwindcss
executable by setting aTAILWINDCSS_INSTALL_DIR
environment variable. (#224, #226) by @flavorjones
- Installer now includes all 5 official Tailwind plugins (adding
line-clamp
andcontainer-queries
). (#254) by @Kentasmic
- When Rails CSS compression is on, avoid generating minified tailwindcss assets. (#253) by @flavorjones.
- Update to Tailwind CSS v3.2.7 by @flavorjones.
- Update to Tailwind CSS v3.2.6 by @flavorjones.
- Introduce a
verbose
task argument, and put verbose logging behind it by @ghiculescu. - Fix scaffold view generation for nested models (#227) by @dixpac.
- Improved documentation by @ghiculescu and @flavorjones.
- Update to Tailwind CSS v3.2.4 by @flavorjones.
- Update to Tailwind CSS v3.2.3 by @willcosgrove.
- Update
bin/dev
script to stay in sync with other Rails installers' versions (e.g,cssbundling-rails
anddartsass-rails
). Usesh
instead ofbash
for vanilla Alpine support, and useexec
to run foreman for better interrupt handling. #219 by @marcoroth.
- Update to Tailwind CSS v3.2.2 by @AlexKovynev.
- Add
arm-linux
support. #218 by @flavorjones.
- Update to Tailwind CSS v3.2.1 by @AlexKovynev in #213.
- Update to Tailwind CSS v3.2.0 by @domchristie in #209.
- Work around upstream rubygems issue on
musl
platforms. [#200]
- Correctly handle paths with embedded spaces. #184 by @flavorjones
- The
build
andwatch
tasks accept adebug
argument to generate unminified assets:rails tailwindcss:build[debug]
orrails tailwindcss:watch[debug]
. #198 by @flavorjones - The
watch
task accepts apoll
argument to use polling instead of file system events:rails tailwindcss:watch[poll]
. #199 by @flavorjones
- Use exec to run tailwind binary, so return codes pass through by @blerchin in #181
- Update to Tailwind CSS v3.1.8 by @TastyPi in #186
- Fixed that released gems include the correct version of Tailwind CSS (3.1.3, not 3.0.3) by @dhh
- Update to Tailwind CSS v3.1.3 by @cover in #174
- Add the
public/*.html
path to tailwind content config: by @Edouard-chin in #178 - Allow for spaces in the working directory for build/watch task by @rakaur in #176
- support x64-mingw-ucrt for Ruby 3.1 users (#172) by @flavorjones in #173
- Restrict views to common template formats by @pixeltrix in #155
- Update rake build command to work with Windows by @pietmichal in #156
- Upgrade to Tailwind 3.0.23 by @dhh
- Installer: don't add main in existing projects by @shafy in #146
- Delete legacy tailwind.css by @HusseinMorsy in #148
- Upgrade to Tailwind CSS v3.0.15
- Fix: Insert centring container around the yield by @dixpac in #106
- Add description to watch task by @RolandStuder in #130
- Fix the wrong indentation by @dixpac in #132
- fix: name the platform using just architecture and os by @flavorjones in #103
- Add tailwindcss-linux-arm64 support (make docker on Apple Silicon M1 workflow possible) by @schmidp in #112
- Upgrade to Tailwind CSS 3.0.7 by @dhh
- Remove setting the
dark-mode
explicitly by @dixpac in #100
- Remove redundant font-size class from generators by @marcushwz in #97
- Add error messages on unsupported platforms or when bundler platforms aren't correct by @flavorjones in #102
Tailwind CSS for Rails now uses the standalone executables made for Tailwind 3. These executables are platform specific, so there's actually separate underlying gems per platform, but the correct gem will automatically be picked for your platform. Supported platforms are Linux x64, macOS arm64, macOS x64, and Windows x64. (Note that due to this setup, you must install the actual gems – you can't pin your gem to the github repo.)
This is a completely different approach from previous versions of tailwindcss-rails. Gone is Ruby-powered purger. Everything now works as it would if you had installed the Node version of Tailwind. But without the Node!
This setup requires a separate watch process to run, which is configured and modeled after the approach used in cssbundling-rails. Look at the README for more details.
Huge thanks to @flavorjones for creating the platform-specific gem setup 🙏
Nothing. But we're promote 0.5.4 to 1.0.0 to go along with the final release of Rails 7.0. Because as a new sanctioned default option of Rails 7, we should stick to the API, and this communicates that 🚀🥳
- Only depends on the
railties
gem.
- Match button label for destroy with text used by regular Rails templates by @dhh