Skip to content

Conversation

@achmiral
Copy link

No description provided.

@dhh
Copy link
Member

dhh commented Apr 30, 2022

What's the purpose of not just keeping it consistent?

@achmiral
Copy link
Author

achmiral commented May 1, 2022

It's a little bit hard to debug when the --minify flag is on. For example when the styling is not applied on some element. So I have to check whether the class or styling has been generated or not in chrome developer tools or in "tailwind.css", especially for custom classes defined using the @layer component directive.

@ur5us
Copy link

ur5us commented May 16, 2022

To add another data point: I’m combining Bootstrap v3 with Tailwind in app. Admittedly, just is just a transition period. Anyway, Bootstrap v3 and many other CSS frameworks make their own assumptions by using a particular CSS reset for instance which usually includes CSS declarations for html { … } and body { … }. In those case, debugging with a minified Tailwind build is tricky.

@flavorjones
Copy link
Member

flavorjones commented Sep 3, 2022

I've created #198 which implements this feature more flexibly.

@flavorjones flavorjones closed this Sep 3, 2022
flavorjones added a commit that referenced this pull request Sep 3, 2022
@flavorjones
Copy link
Member

v2.0.13 has this feature, please see the README for an explanation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants