Currently, our styles don't sit within any CSS layers outside of dotcom. When used with tools like @primer/tailwind-config, this means that it is non-trivial to use a tailwind class with a component since the tailwind utility class will always lose in specificity (because it is wrapped in a layer)
This issue tracks adding support for this directly into primer/react and removing this from dotcom by following our CSS layers ADR.
Currently, our styles don't sit within any CSS layers outside of dotcom. When used with tools like
@primer/tailwind-config, this means that it is non-trivial to use a tailwind class with a component since the tailwind utility class will always lose in specificity (because it is wrapped in a layer)This issue tracks adding support for this directly into primer/react and removing this from dotcom by following our CSS layers ADR.