unocss
unplugin-vue-components
Our great sponsors
unocss | unplugin-vue-components | |
---|---|---|
56 | 18 | |
15,386 | 3,509 | |
2.6% | 2.7% | |
9.6 | 7.0 | |
6 days ago | about 1 month ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
unocss
-
Tailwind CSS v4.0.0 Alpha
I wish tailwind would support attributify like https://github.com/unocss/unocss, which is much more readable for complex layouts:
link
- UnoCSS — an Instant On-Demand Atomic CSS Engine
-
Catalyst – Tailwind CSS Application UI Kit
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/
-
What do you think we can do better to improve Vue position in the frontend space as a dominant UI framework?
I think UnoCss is may be better than Tailwind already and has a good Vue integration https://unocss.dev/
-
~~New~~ Old way to write CSS
The most popular tools that implement this approach are: Tailwind, WindiCSS, UnoCSS.
-
Which is best for DX and efficiency, TailwindCSS, UnoCSS, PandaCSS, or the new MasterCSS
- UnoCSS: https://unocss.dev/
-
A design system for the federal government
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/ ♥
-
Modern CSS Framework or Library for Static Websites?
UnoCSS is a popular option
-
Vrite Editor: Open-Source WYSIWYG Markdown Editor
UnoCSS — for styling with Tailwind-like atomic CSS;
-
Why I Switched From Neovim to VSCode
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.
unplugin-vue-components
- Vue 3 vs Vue 2 so far? What's your opinion? Things I didn't like about Vue 3 compared to Vue 2
-
Saw this on twitter last night 😂😂
unplugin-vue-components, auto import components in the src/components path.
-
Does anyone uses nvim?
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
- How to register all the components in subfolders?
-
Import commonly-used module once, not in each component?
Add in unplugin-vue-components and you cut away a lot of boilerplate import nonsense.
-
Amatuer question - I'm using PrimeVUE to create a UI, do I need to import each control I'm using?
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.
-
Do I need Quasar CLI If I only need Quasar's components and nothing else ?
I can recommend unplugin-vue-components with the quasar resolver
-
Can I import all components in a particular folder with one "import" statement?
As someone mentioned unplugin-vue-components.
- Jak przejść z Webpack (Vue CLI) na Vite?
-
Vue 3 - UI Framework for large desktop app (Quasar or element plus + vuetify alpha?)
I'd like to add https://github.com/antfu/unplugin-icons and https://github.com/antfu/unplugin-vue-components.
What are some alternatives?
Tailwind CSS - A utility-first CSS framework for rapid UI development.
unplugin-auto-import - Auto import APIs on-demand for Vite, Webpack and Rollup
windicss - Next generation utility-first CSS framework.
unplugin-icons - 🤹 Access thousands of icons as components on-demand universally.
tail-kit - Tail-kit is a free and open source components and templates kit fully coded with Tailwind css 3.0.
vite-imagetools - Load and transform images using a toolbox :toolbox: of custom import directives!
Quasar Framework - Quasar Framework - Build high-performance VueJS user interfaces in record time
unplugin-fonts - Universal Webfont loader - Unfonts - based on https://web.dev/optimize-webfont-loading/
vanilla-extract - Zero-runtime Stylesheets-in-TypeScript
vite-quasar-api - spring boot jpa
pico - Minimal CSS Framework for semantic HTML
vite-plugin-pages - File system based route generator for ⚡️Vite