Ability to prefix Primer CSS utilities to avoid TailwindCSS conflict

[mcastilho]

I am struggling using this library since we want to use TailwindCSS as well. But a lot of the CSS utilities conflict with TailwindCSS and it is really hard to pin-point issues.

Is there a way to prefix the CSS utilities in Primer ViewComponents ?

I know I can prefix TailwindCSS but most of our designs are using tailwind and we would like to have both. That way ViewComponent doesn't affect the rest of our CSS utilities that are already in use.

[jonrohan]

@mcastilho Thanks for the issue. We don't use TailwindCSS internally but can understand the frustration with the conflicting classnames. We've tried to previously remove our use of Primer utilities in the components, but we've been reduced in the amount of work we can tackle. If there's any specific components that continually give you trouble, I would accept any changes where you replace something like mb-0 with a new class in the corresponding component .pcss file.

It's a bigger lift to get our build system on par with Tailwind's system adding prefixing.