Closed WildEgo closed 3 years ago
Hi Luis, thanks for reporting that. I think I know what's causing that. I've pushed a fix for it with a major release which uses PostCSS 8.
I really need to refactor the plugin for a better way of checking for compatible values for width, but let me know if version 2.0.0 solves this issue.
Many thanks, Gavin
Hi Luis, thanks for reporting that. I think I know what's causing that. I've pushed a fix for it with a major release which uses PostCSS 8.
I really need to refactor the plugin for a better way of checking for compatible values for width, but let me know if version 2.0.0 solves this issue.
Many thanks, Gavin
I'll check it as soon as I can, thanks a lot I'll update u with what I find!
Heads up it has problems with "width: max-content" but no problem I didn't need that one anyway personally.
Doh, sorry about that. When I get chance over the weekend. I'll fix it properly. It's not even really needed unless you're using percentages, so I might add an option to disable if not using percentage gaps.
@WildEgo thanks for your help raising this issue. I've updated it with a much better check for units now, so max-content
should work also. Thanks agin.
Hey I just wanted to try this package and found out and found this little problem, for context my PostCSS version on package.json is
^8.2.2
.The error:
The setup for postcss below (flexgap standing for flex-gap-polyfill):
Regards, Luis Bizarro.