Overview
Ember CLI Tailwind was created with the aim of simplifying the integration of Tailwind CSS into Ember applications. The developer intended to allow users to set up Tailwind with minimal hassle, encapsulating PostCSS configuration within the addon’s framework. However, as the library evolved, the need for more user control and flexibility in PostCSS configuration became evident, leading to its eventual deprecation.
This update reflects a shift towards a more direct engagement with the tools that developers utilize, emphasizing the importance of the official documentation and encouraging a move away from custom add-ons that may not align with the latest practices. As users transition away from Ember CLI Tailwind, understanding the underlying mechanics of Tailwind and PostCSS is encouraged for a more sustainable and adaptable development experience.
Features
- Simple Integration: Initially designed to allow a one-liner setup for adding Tailwind CSS to Ember apps.
- Encapsulated PostCSS Configuration: Handled PostCSS behind the scenes, abstracting complexity from the user experience.
- Flexibility Encouraged: Underlines the necessity for users to configure PostCSS themselves, enabling the use of tools like Autoprefixer and PurgeCSS.
- Updated Tailwind Practices: Aligns with Tailwind’s shift towards an empty configuration file and encourages the use of official documentation.
- Decommissioning Support: Acknowledges the deprecation of the add-on and provides resources for migrating to a more robust solution.
- Community Driven: Advocates for an approach that connects Ember users more closely with the broader Tailwind community’s ongoing developments.
- Seamless Transition: Guides are available to help facilitate the migration away from Ember CLI Tailwind to using ember-cli-postcss for future projects.
