Releases: rails/tailwindcss-rails
v2.0.9
What's Changed
- 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
Full Changelog: v2.0.8...v2.0.9
v2.0.8
What's Changed
- 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
Full Changelog: v2.0.7...v2.0.8
v2.0.7
What's Changed
- Installer: don't add main in existing projects by @shafy in #146
- Delete legacy tailwind.css by @HusseinMorsy in #148
Full Changelog: v2.0.6...v2.0.7
v2.0.6
v2.0.5
v2.0.3
What's Changed
- 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
New Contributors
Full Changelog: v2.0.2...v2.0.3
v2.0.2
What's Changed
- Upgrade to Tailwind CSS 3.0.7 by @dhh
- Remove setting the
dark-mode
explicitly by @dixpac in #100
Full Changelog: v2.0.1...v2.0.2
v2.0.1
What's Changed
- 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
Full Changelog: v2.0.0...v2.0.1
v2.0.0
What's Changed
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 π
Full Changelog: v1.0.0...v2.0.0