Background
Currently, I'm exploring ways to disable the built-in utility classes in favor of using unocss (or TailwindCSS via unocss presets) in my project. I’ve found some related behavior:
Goal
In my project, I aim to:
- ✅ Use
unocss instead of built-in utility classes wherever possible
- ❌ Disable Vuetify utility classes selectively — only when safe
- 🧱 For unsafe cases, block them via
unocss’s blocklist
Problem
Currently, I’m unclear on the compatibility boundaries between Vuetify utility classes and unocss. Specifically:
- Which Vuetify utility classes are safe to disable?
- Which utility classes should be explicitly blocked in
unocss to avoid conflicts?
Proposed Idea
Would it be possible to:
- Provide a Vuetify-compatible UnoCSS preset or config helper
- Or publish an official list of utility classes that:
- ✅ Can be safely replaced by
unocss
- 🧱 Should be included in a
blocklist
This would greatly help in customizing and reducing conflicts when using unocss in Vuetify-based projects.
Question
Has anyone already explored this direction?
Any recommended strategy or best practice for gradually migrating to unocss with minimal friction?
Thanks in advance!
Background
Currently, I'm exploring ways to disable the built-in utility classes in favor of using
unocss(or TailwindCSS viaunocsspresets) in my project. I’ve found some related behavior:unocssvia a preset, which is great!Goal
In my project, I aim to:
unocssinstead of built-in utility classes wherever possibleunocss’sblocklistProblem
Currently, I’m unclear on the compatibility boundaries between Vuetify utility classes and
unocss. Specifically:unocssto avoid conflicts?Proposed Idea
Would it be possible to:
unocssblocklistThis would greatly help in customizing and reducing conflicts when using
unocssin Vuetify-based projects.Question
Has anyone already explored this direction?
Any recommended strategy or best practice for gradually migrating to
unocsswith minimal friction?Thanks in advance!