An Ember CLI addon that integrates Tailwind CSS into Ember apps and addons with automatic configuration and a styleguide.
Ember CLI Tailwind is a deprecated Ember addon that integrates Tailwind CSS into Ember applications and addons. It automatically configures PostCSS and Tailwind, providing a one-liner setup with rebuilds and a visual styleguide. The project aimed to simplify Tailwind adoption but now recommends using ember-cli-postcss for direct control.
Ember developers who want to use Tailwind CSS in their apps or addons without manual PostCSS configuration.
It offered a quick, opinionated setup for Tailwind in Ember with an interactive styleguide, but now encourages using standard tools for flexibility and sustainability.
Adds Tailwind CSS to your app or addon
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Adds Tailwind CSS with a single `ember install` command, automatically configuring PostCSS and enabling rebuilds, as shown in the installation section for minimal setup effort.
Includes a built-in `/tailwind` route that visually displays all configured styles and updates in real-time during development, useful for quick reference and testing.
Allows defining new utility classes and Tailwind components in dedicated directories like `app/tailwind/utilities`, with automatic inclusion in the build without manual configuration.
Provides a `build-tailwind` function for custom build integration, enabling use cases like Sass compatibility and explicit imports in addons, as detailed in the advanced usage section.
The project is explicitly deprecated as of August 2019, meaning no updates, bug fixes, or support for newer dependencies, making it risky for production use.
It abstracts PostCSS configuration behind the scenes, which the README admits makes it difficult to add other PostCSS plugins or tweak settings, pushing users toward ember-cli-postcss for control.
Uses a scaffolded config in separate files, conflicting with Tailwind's current recommendation of starting with an empty config, which can lead to inconsistencies and extra maintenance.