fix: tailwindcss config (#7693)

* 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

View File

@@ -28,6 +28,7 @@
"devDependencies": {
"@nolebase/vitepress-plugin-git-changelog": "catalog:",
"@tailwindcss/vite": "catalog:",
"@vben/tailwind-config": "workspace:*",
"@vben/vite-config": "workspace:*",
"@vite-pwa/vitepress": "catalog:",
"vitepress": "catalog:",

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.

View File

@@ -6,7 +6,7 @@
项目当前不再通过 `tailwind.config.*` 文件维护 Tailwind 配置,主题与扫描范围都统一放在 CSS 与共享 Vite 配置中。
- 主题入口:`packages/@core/base/design/src/css/global.css`
- 主题入口:`internal/tailwind-config/src/theme.css`
- Vite 集成:`internal/vite-config`
`global.css` 中你会看到当前项目使用的 Tailwind CSS v4 指令,例如:
@@ -21,7 +21,7 @@
当前项目不会根据某个包下是否存在 `tailwind.config.mjs` 来决定是否启用 Tailwind CSS。
应用和包统一复用 `@vben/vite-config`,并由该配置接入 `@tailwindcss/vite`。Tailwind 的扫描范围则统一在 `packages/@core/base/design/src/css/global.css` 中维护。
应用和包统一复用 `@vben/vite-config`,并由该配置接入 `@tailwindcss/vite`。Tailwind 的扫描范围则统一在 `@vben/tailwind-config` 对应的 `internal/tailwind-config/src/theme.css` 中维护。
::: tip 包使用 Tailwind CSS 的说明
@@ -35,4 +35,4 @@
- `internal/vite-config/src/plugins/tailwind-reference.ts`
当组件样式中使用 `@apply` 时,会自动注入对应的 `@reference`,一般不需要手动补充。
当组件样式中使用 `@apply` 时,会自动注入 `@reference "@vben/tailwind-config/theme"`,一般不需要手动补充。