You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a PR looking to solve for this #3009 however I figured I would still raise the issue.
Having Nuxt UI respect the tailwind prefix would be handy to have to not overlap styles if components are being utilised on pages that already have existing styles with the same name and are not using tailwind.
Additional context
No response
The text was updated successfully, but these errors were encountered:
This is super important, we need to use TW prefixes because the application we want to integrate our SPA into uses custom tailwind classes with !important. Without the prefixes the UI will not work
Somehow it is probably more important to overwrite a TW Color Token System instead of offering prefixes - which Tailwind has implemented for a reason. Not everyone needs this, but anyone who has to integrate their app into another application often experiences nasty surprises.
If nothing happens here, we will switch to Shadcn, which offers prefixing.
Description
There is a PR looking to solve for this #3009 however I figured I would still raise the issue.
Having Nuxt UI respect the tailwind prefix would be handy to have to not overlap styles if components are being utilised on pages that already have existing styles with the same name and are not using tailwind.
Additional context
No response
The text was updated successfully, but these errors were encountered: