unplugin-vue-components VS unocss

unplugin-vue-components, auto import components in the src/components path.

One suggestion I have though to make your life easier is to add the unplugin plugin to your app and then you won't have to list all the components you are importing. https://github.com/antfu/unplugin-vue-components

Add in unplugin-vue-components and you cut away a lot of boilerplate import nonsense.

Presumably you're using Vite so you can check out unplugin-vue-components and the Prime Vue resolver. This should enable you to simply use whatever component you want within your template and Vite will auto import it for you without having to explicitly do so yourself.

I can recommend unplugin-vue-components with the quasar resolver

As someone mentioned unplugin-vue-components.

I'd like to add https://github.com/antfu/unplugin-icons and https://github.com/antfu/unplugin-vue-components.

I wish tailwind would support attributify like https://github.com/unocss/unocss, which is much more readable for complex layouts:

  link

I feel the same about people praising Tailwind.

Tailwind (and similar, I tend to use https://unocss.dev/) is not good for your frontend architecture BUT they allow you to be so fast, that it negates the benefits.

For a job well done, I'd follow the principles of https://maintainablecss.com/

I think UnoCss is may be better than Tailwind already and has a good Vue integration https://unocss.dev/

The most popular tools that implement this approach are: Tailwind, WindiCSS, UnoCSS.

- UnoCSS: https://unocss.dev/

haha, fair point. Still, I'm on the fence about how utility components are namespaced in USWDS. Perhaps giving users the flexibility to define the namespace might work better? One thing that bugs me is the absence of class-sorting like we have in TailwindCSS. Plus, there are some gaps I've noticed in USWDS. The naming, especially when comparing "padding-x-2" and "p-x-2", can be really annoying when switching around, maybe that could also be an option for the developer or project. Similar to the ideas antfu has on uno.css https://unocss.dev/ ♥

UnoCSS is a popular option

UnoCSS — for styling with Tailwind-like atomic CSS;

Some exceptional libraries and frameworks only support VSCode, which you could argue is a bad thing, but it makes sense, VSCode is the most popular code editor after all. For example UnoCSS only has a VSCode extension, and it's my favourite way to write CSS. Astro has a LSP but I've found that the experience in VSCode is much better than in Neovim.