Closed cowboycodr closed 5 months ago
Additionally I just realized that in some instances it is even producing the same (invalid) styles multiple times:
[class ~ ="not-prose"] *)) {
margin-top: 1.25em;
}
[class ~ ="not-prose"] *)) {
margin-bottom: 1.25em;
}
[class ~ ="not-prose"] *)) {
margin-top: 1.25em;
}
[class ~ ="not-prose"] *)) {
margin-bottom: 1.25em;
}
I apologize. I spoke too soon and just read the part where it says that this isn't really possible for the exact reasons stated in this issue.
Nevertheless, it would be really cool/useful to add support for @tailwindcss/typography
(if it is at all possible).
As brought up in the conversation attached: Maizzle doesn't handle
@tailwindcss/typography
plugin well, and mostly produces invalid HTML/CSS.Here's an example:
As you can see, there are many invalid CSS selectors, as well not all of the styles are inlined which wouldn't work for popular email clients such as Gmail.
For more context here is my
config.production.js
:Discussed in https://github.com/orgs/maizzle/discussions/1240