You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should it be possible today to use maizzle (2.5.1) with tailwindcss@canary?
This would allow us to use the JIT correctly respecting disabled opacity plugins, without depending on a new maizzle release (tailwindlabs/tailwindcss#4071).
I tried overwriting maizzle's tailwindcss dependency with npm-shrinkwrap, but it had no affect.
The text was updated successfully, but these errors were encountered:
Maizzle needs to keep a tight check on the Tailwind version being used, since even feature releases can cause issues. New Tailwind version should be out soon though, I think - I'll add support right away once it does.
Should it be possible today to use maizzle (2.5.1) with tailwindcss@canary?
This would allow us to use the JIT correctly respecting disabled opacity plugins, without depending on a new maizzle release (tailwindlabs/tailwindcss#4071).
I tried overwriting maizzle's tailwindcss dependency with npm-shrinkwrap, but it had no affect.
The text was updated successfully, but these errors were encountered: