Windi CSS for Nuxt.js! β‘οΈ
Next generation utility-first CSS framework.
Status: Stable v2 β , bridge β , v3 β Made possible by my Sponsor Program π Follow me @harlan_zw π¦ |
- 𧩠On-demand CSS utilities (Compatible with Tailwind CSS v2) and native elements style resetting
- π Use directives in any CSS lang
@apply
,@variants
,@screen
,@layer
,theme()
(Note: Vite / Nuxt v3 has limited support) - π³ Support Utility Groups - e.g.
bg-gray-200 hover:(bg-gray-100 text-red-300)
- π§βπ€βπ§ Plays nicely with Nuxt v3, Nuxt v2, @nuxt/vite and @nuxt/content
- π Integrated with windicss-analysis
npx nuxi@latest module add windicss
Note: If you're using Nuxt v2, you should stay on the 2.x tags: npm install nuxt-windicss@2
.
Within your nuxt.config.js
add the following.
// nuxt.config.js
export default {
buildModules: [
'nuxt-windicss',
],
}
import { defineNuxtConfig } from 'nuxt3'
export default defineNuxtConfig({
modules: [
'nuxt-windicss',
],
})
For Nuxt config typescript support, add the module within your tsconfig.json
.
{
"compilerOptions": {
"types": [
"nuxt-windicss"
]
}
}
Add the import with your existing windi imports and you'll have autocompletion in your Chrome DevTools! See "Design in DevTools" for more information.
export default {
// ...
css: [
'virtual:windi.css',
'virtual:windi-devtools',
],
}
An analyser tool for Windi CSS. Browse your utilities usages, have an overview of your design system, identify "bad practices", and more!
You can enable Windi Analzyer using the Nuxt config. The analyser is only available in development mode.
export default defineNuxtConfig({
buildModules: [
'nuxt-windicss',
],
windicss: {
analyze: true
}
})
Alternatively, you can provide an object to control the analysis or the server.
windicss: {
analyze: {
analysis: {
interpretUtilities: false,
},
// see https://github.com/unjs/listhen#options
server: {
port: 4444,
open: true,
}
}
}
This module won't work with @nuxtjs/tailwindcss
, you will need to remove it.
buildModules: [
- '@nuxtjs/tailwindcss',
],
If you have a tailwind.config.js
, please rename it to windi.config.js
or windi.config.ts
.
Follow the migration guide for other change details.
By default, this all windi layers will be automatically imported for you.
If you'd like to change the layout ordering you can include the layers in any order you like.
For example, if you had a main.css
which had h1 { margin-bottom: 30px; }
, you might do something like this:
// nuxt.config.js
export default {
// ...
css: [
// windi preflight
'virtual:windi-base.css',
// your stylesheets which overrides the preflight
'@/css/main.css',
// windi extras
'virtual:windi-components.css',
'virtual:windi-utilities.css',
],
}
Read the documentation for more details.
- Windy team
- @antfu Based on his Rollup / Vite implementation & his util package
MIT License Β© 2021 Harlan Wilton