Currently, the library publishes styles in @gausszhou/vue3-drag-resize-rotate/lib/bundle.esm.css as .vue-drag-resize-rotate[data-v-3c286975] { ... }
This makes it inconvenient to override (amend) the styles in the project. One either have to copy the scope selector (which is error prone, as the scope ID is auto generated and will change on every package update), or trick CSS to narrow the selector with some sort of hack, for instance :root .vue-drag-resize-rotate { ... }
In my thinking, library solutions should not be using scoped (or module) styles. The library styles are supposed to have a well recognizable place in the global scope, so that user could easily override them without additional hacks.
Currently, the library publishes styles in
@gausszhou/vue3-drag-resize-rotate/lib/bundle.esm.cssas.vue-drag-resize-rotate[data-v-3c286975] { ... }This makes it inconvenient to override (amend) the styles in the project. One either have to copy the scope selector (which is error prone, as the scope ID is auto generated and will change on every package update), or trick CSS to narrow the selector with some sort of hack, for instance
:root .vue-drag-resize-rotate { ... }In my thinking, library solutions should not be using scoped (or module) styles. The library styles are supposed to have a well recognizable place in the global scope, so that user could easily override them without additional hacks.