- Update to Tailwind CSS v3.2.4 by @flavorjones.
- Update to Tailwind CSS v3.2.3 by @willcosgrove.
- Update
bin/devscript to stay in sync with other Rails installers' versions (e.g,cssbundling-railsanddartsass-rails). Useshinstead ofbashfor vanilla Alpine support, and useexecto run foreman for better interrupt handling. #219 by @marcoroth.
- Update to Tailwind CSS v3.2.2 by @AlexKovynev.
- Add
arm-linuxsupport. #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
muslplatforms. [#200]
- Correctly handle paths with embedded spaces. #184 by @flavorjones
- The
buildandwatchtasks accept adebugargument to generate unminified assets:rails tailwindcss:build[debug]orrails tailwindcss:watch[debug]. #198 by @flavorjones - The
watchtask accepts apollargument 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/*.htmlpath 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-modeexplicitly 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
railtiesgem.
- Match button label for destroy with text used by regular Rails templates by @dhh