UnoCSS
The instant on-demand Atomic CSS engine.
💡 I highly recommend reading this blog post - Reimagine Atomic CSS for the story behind this tool.
Try it!
🤹♂️ Online Playground
Features
Inspired by Windi CSS, Tailwind CSS, Twind but:
- Fully customizable - no core utilities, all functionalities are provided via presets.
- No parsing, no AST, no scanning, it's INSTANT (200x faster than Windi CSS or Tailwind JIT)
- <3kb min+gzip - zero deps and browser friendly.
- Shortcuts - aliasing utilities, dynamically.
- Attributify Mode - group utilities in attributes
- Pure CSS Icons - use any icon as a single class.
- CSS Scoping
- Code-splitting for CSS - ships minimal CSS for MPA.
- Library friendly - ships atomic styles with your component libraries and safely scoped.
Benchmark
10/21/2021, 2:17:45 PM
1656 utilities | x50 runs (min build time)
none 8.75 ms / delta. 0.00 ms
unocss v0.0.0 13.72 ms / delta. 4.97 ms (x1.00)
windicss v3.1.9 980.41 ms / delta. 971.66 ms (x195.36)
tailwindcss v3.0.0-alpha.1 1258.54 ms / delta. 1249.79 ms (x251.28)
Non-goal
UnoCSS is designed NOT to be/have:
- Align with Tailwind - technically, UnoCSS is flexible enough to do that, but it's not a priority.
- A CSS preprocessor (e.g.
@apply
) - but you can use shortcuts. - Tailwind's plugin system - but you can write custom rules in seconds and share them as presets!
- Integrations for Webpack or others - it's Vite only (at this moment)
Disclaimer
🧪 This package is trying to explore the possibilities of what an atomic CSS framework can be. Not production-ready, yet. Expect breaking changes and overhaul redesigns.
Installation
npm i -D unocss
import Unocss from 'unocss/vite'
export default {
plugins: [
Unocss({ })
]
}
Add uno.css
to your main entry:
import 'uno.css'
That's it, have fun.
Configurations
UnoCSS is an atomic-CSS engine instead of a framework. Everything is designed with flexibility and performance in mind. In UnoCSS, there are no core utilities; all functionalities are provided via presets.
By default, UnoCSS applies the default preset. Which provides a common superset of the popular utilities-first framework, including Tailwind CSS, Windi CSS, Bootstrap, Tachyons, etc.
For example, both ml-3
(Tailwind), ms-2
(Bootstrap), ma4
(Tachyons), mt-10px
(Windi CSS) are valid.
.ma4 { margin: 1rem; }
.ml-3 { margin-left: 0.75rem; }
.ms-2 { margin-inline-start: 0.5rem; }
.mt-10px { margin-top: 10px; }
Learn more about the default preset.
Presets
Presets are the heart of UnoCSS that lets you make your own custom framework in minutes. We are providing the following presets officially:
To set presets to your project:
import Unocss from 'unocss/vite'
import { presetUno, presetAttributify, presetWind } from 'unocss'
export default {
plugins: [
Unocss({
presets: [
presetAttributify({ }),
presetUno(),
]
})
]
}
When the presets
option is specified, the default preset will be ignored.
To disable the default preset, you can set presets
to an empty array:
import Unocss from 'unocss/vite'
export default {
plugins: [
Unocss({
presets: [],
rules: [
]
})
]
}
Custom Rules
Static Rules
Writing custom rules for UnoCSS is super easy. For example:
rules: [
['m-1', { margin: '0.25rem' }]
]
You will have the following CSS generated whenever m-1
is detected in users' codebase:
.m-1 { margin: 0.25rem; }
Dynamic Rules
To make it smarter, change the matcher to a RegExp and the body to a function:
rules: [
[/^m-(\d+)$/, ([, d]) => ({ margin: `${d / 4}rem` })],
[/^p-(\d+)$/, (match) => ({ padding: `${match[1] / 4}rem` })],
]
The first argument of the body function is the match result, you can destructure it to get the matched groups.
For example, with the following usage:
<div class="m-100">
<button class="m-3">
<icon class="p-5" />
My Button
</button>
</div>
the corresponding CSS will be generated:
.m-100 { margin: 25rem; }
.m-3 { margin: 0.75rem; }
.p-5 { padding: 1.25rem; }
Congratulations! Now you got your own powerful atomic CSS utilities, enjoy!
Full Controlled Rules
It's an advance feature, you should not need it in most of the cases.
When you really need some advanced rules that can't be covered by the combination of Dynamic Rules and Variants, you also provide a way to give you full controls of generating the CSS.
By returning a string
from the dynamic rule's body function, it will be directly passed to the generated CSS. That also means you would need to take care of things like CSS escaping, variants applying, CSS constructing, and so on.
import Unocss, { escape as e } from 'unocss'
Unocss({
rules: [
[/^custom-(.+)$/, ([, name], { rawSelector, currentSelector, variantHandlers, theme }) => {
if (name.includes('something'))
return
if (variantHandlers.length)
return
return `
.${e(rawSelector)} {
font-size: ${theme.fontSize.sm};
}
/* you can have multiple rules */
.${e(rawSelector)}::after {
content: 'after';
}
.foo > .${e(rawSelector)} {
color: red;
}
/* or media queries */
@media (min-width: ${theme.breakpoints.sm}) {
.${e(rawSelector)} {
font-size: ${theme.fontSize.sm};
}
}
`
}]
]
})
Note is an advanced feature, you might need to read some code to take the full power of it.
Ordering
UnoCSS keeps the order of the rules you defined to the generated CSS. Later ones come with higher priority.
Shortcuts
UnoCSS provides the shortcuts functionality that is similar to Windi CSS's
shortcuts: {
'btn': 'py-2 px-4 font-semibold rounded-lg shadow-md',
'btn-green': 'text-white bg-green-500 hover:bg-green-700',
'red': 'text-red-100'
}
In addition to the plain mapping, UnoCSS also allows you to define dynamic shortcuts.
Similar to Rules, a dynamic shortcut is the combination of a matcher RegExp and a handler function.
shortcuts: [
{
'btn': 'py-2 px-4 font-semibold rounded-lg shadow-md',
},
[/^btn-(.*)$/, ([, c]) => `bg-${c}-400 text-${c}-100 py-2 px-4 rounded-lg`],
]
With this, we could use btn-green
and btn-red
to generate the following CSS:
.btn-green {
padding-top: 0.5rem;
padding-bottom: 0.5rem;
padding-left: 1rem;
padding-right: 1rem;
--un-bg-opacity: 1;
background-color: rgba(74, 222, 128, var(--un-bg-opacity));
border-radius: 0.5rem;
--un-text-opacity: 1;
color: rgba(220, 252, 231, var(--un-text-opacity));
}
.btn-red {
padding-top: 0.5rem;
padding-bottom: 0.5rem;
padding-left: 1rem;
padding-right: 1rem;
--un-bg-opacity: 1;
background-color: rgba(248, 113, 113, var(--un-bg-opacity));
border-radius: 0.5rem;
--un-text-opacity: 1;
color: rgba(254, 226, 226, var(--un-text-opacity));
}
Rules Merging
By default, UnoCSS will merge CSS rules with the same body to minimize the CSS size.
For example, <div class="m-2 hover:m2">
will generate
.hover\:m2:hover, .m-2 { margin: 0.5rem; }
instead of two separate rules:
.hover\:m2:hover { margin: 0.5rem; }
.m-2 { margin: 0.5rem; }
Style Resetting
UnoCSS does not provide style resetting or preflight by default for maximum flexibility and does not populate your global CSS. If you use UnoCSS along with other CSS frameworks, they probably already do the resetting for you. If you use UnoCSS alone, you can use resetting libraries like Normalize.css.
We also provide a small collection for you to grab them quickly:
npm i @unocss/reset
import '@unocss/reset/normalize.css'
import '@unocss/reset/eric-meyer.css'
import '@unocss/reset/tailwind.css'
Custom Variants
Variants allows you to apply some variations to your existing rules. For example, to implement the hover:
variant from Tailwind:
variants: [
(matcher) => {
if (!matcher.startsWith('hover:'))
return matcher
return {
matcher: matcher.slice(6),
selector: s => `${s}:hover`,
}
}
],
rules: [
[/^m-(\d)$/, ([, d]) => ({ margin: `${d / 4}rem` })],
]
match
controls when the variant is enabled. If the return value is a string, it will be used as the selector for matching the rules.selector
provides the availability of customizing the generated CSS selector.
Let's have a tour of what happened when matching for hover:m-2
:
hover:m-2
is extracted from users usageshover:m-2
send to all variants for matchinghover:m-2
is matched by our variant and returns m-2
- the result
m-2
will be used for the next round of variants matching - if no more variant is matched,
m-2
will then goes to match the rules - our first rule get matched and generates
.m-2 { margin: 0.5rem; }
- finally, we apply our variants transformation to the generated CSS. In this case, we prepended
:hover
to the selector
hook
As a result, the following CSS will be generated:
.hover\:m-2:hover { margin: 0.5rem; }
With this, we could have m-2
applied only when users hover over the element.
The variant system is very powerful and can't be covered fully in this guide, you can check the default preset's implementation to see more advanced usages.
CSS Scoping
🚧 This part is still under experiment. You might want to read the code to see how it works currently.
Acknowledgement
in alphabet order
License
MIT License © 2021 Anthony Fu