Fix color generation compatibility with chroma-js v3#211
Merged
Conversation
maxiadlovskii
approved these changes
Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
chroma-js v3 changed the output of
.css()to use CSS Color Level 4 space-separated syntax (rgb(r g b / a)) instead of the legacy comma-separated format (rgba(r, g, b, a)). This broke Mantine v8's internal color parser (toRgba), which only handles comma-separated input — causing hover states on default buttons to render an invalid color (rgba(173879298, 0, NaN, 1)).Replace all
.css()calls inopacify,contrastingColor,colorLevel, andinputColorswith.hex(), which produces output (#rrggbbaafor semi-transparent,#rrggbbfor opaque) that is compatible with both Mantine's parser and the browser. Regeneratetheme.jsonwith the updated utilities.Before:
After:
