nailaoyun/nl-admin-view
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

fix: tailwindcss config (#7693)

Browse Source 
* chore: update deps

* fix: tailwindcss config

* fix: lint

* fix: lint

* chore: update deps
This commit is contained in:
xingyu
2026-03-19 15:51:09 +08:00
committed by GitHub
parent d43a3729c3
commit 0c300d040c
26 changed files with 1257 additions and 1320 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/src/en/guide/project/tailwindcss.md
View File

@@ -6,7 +6,7 @@
The project no longer maintains Tailwind through `tailwind.config.*` files. Theme definitions and scan scope are now managed through CSS and the shared Vite configuration.
- Theme entry: `packages/@core/base/design/src/css/global.css`
- Theme entry: `internal/tailwind-config/src/theme.css`
- Vite integration: `internal/vite-config`
In `global.css`, you will see the Tailwind CSS v4 directives currently used by the project, such as:
@@ -21,7 +21,7 @@ In `global.css`, you will see the Tailwind CSS v4 directives currently used by t
The project does not decide whether Tailwind CSS is enabled based on whether a package contains `tailwind.config.mjs`.
Apps and packages share `@vben/vite-config`, which integrates `@tailwindcss/vite`. The Tailwind scan scope is managed centrally in `packages/@core/base/design/src/css/global.css`.
Apps and packages share `@vben/vite-config`, which integrates `@tailwindcss/vite`. The Tailwind scan scope is managed centrally in `@vben/tailwind-config`, backed by `internal/tailwind-config/src/theme.css`.
::: tip Notes on using Tailwind CSS in packages
@@ -35,4 +35,4 @@ The project applies a shared handling layer for `@apply` inside Vue single-file
- `internal/vite-config/src/plugins/tailwind-reference.ts`
When component styles use `@apply`, the required `@reference` is injected automatically in most cases.
When component styles use `@apply`, `@reference "@vben/tailwind-config/theme"` is injected automatically in most cases.