Just released 1.1.0 with a new, more explicit, behavior of extend_class/3 which fixes the issue mentioned in this topic.
Changelog:
extend_class/3 behavior has been updated and will soon no longer replace default css classes based on their prefix (this behavior is still working but deprecated). To switch to the new behavior and suppress warning messages, pass the prefix_replace: falseoption and use the new ! based syntax to explicitly remove default CSS classes. (ex: !border-* border-red-500)
