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

v1.0.0

What's Changed

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 🚀🥳

0.5.4

• Only depends on the railties gem.

Full Changelog: v0.5.3...v0.5.4

0.5.3

What's Changed

• Match button label for destroy with text used by regular Rails templates by @dhh

Full Changelog: v0.5.2...v0.5.3