[v4] Ordering custom variants and default variants?

[Aurailus]

I like to use custom variants fairly liberally for combining hover and focus-visible states, as well as other things. In Tailwind3, custom variants would have precedence over default ones, but you could redefine the default ones as custom ones to give them higher precedence if you wanted to (which I did for active:, as I want it to supercede my hocus: variants. I tried doing the same in tailwind 4 like below, but it doesn't seem to work the same. Is there any way for me to say that I want active: to have a higher precedence than hocus:?

@custom-variant hocus (&:is(:hover, :focus-visible));
@custom-variant group-hocus (&:is(:hover, :focus-visible) &);
@custom-variant peer-hocus (&:is(:hover, :focus-visible) ~ &);

@custom-variant active (&:active);

[programming-with-ia]

i faced another problem:
how can i turn this to tailwind v4

plugin(function ({ matchUtilities, theme }) {
      const spacing = theme('spacing');

      matchUtilities(
        {
          'fixed-w': (value) => ({
            minWidth: value,
            maxWidth: value,
          }),
          'fixed-h': (value) => ({
            minHeight: value,
            maxHeight: value,
          }),
        },
        {
          values: spacing, // Using Tailwind's spacing scale (px, rem, etc.)
        }
      );
    })

[programming-with-ia]

and also how can use existing variant in @custom-variant

[Aurailus]

Please make your own discussion thread(s), don't hijack this one with unrelated questions.

[programming-with-ia]

@Aurailus
Sorry about that! I thought my question was related to the topic, but I understand now. I'll create a separate discussion thread. Thanks for pointing it out!