feat(theme): migrate to Tailwind CSS variables and refactor theme system#86
feat(theme): migrate to Tailwind CSS variables and refactor theme system#86YESWmeshade wants to merge 6 commits intoDevCloudFE:mainfrom
Conversation
Workspace change through: 41d2ed40 changesets found Planned changes to release
|
| @@ -0,0 +1,16 @@ | |||
| module.exports = { | |||
There was a problem hiding this comment.
This seems to be a misunderstanding. The tailwin.config.js configuration file has been deprecated since tailwind v4, and tailwind 4 actually does not use this file.
| Layout as BasicLayout, | ||
| // getCustomMDXComponent, | ||
| } from "rspress/theme"; | ||
| import "./styles/index.css"; |
There was a problem hiding this comment.
Rspress uses postcss, and we have already configured tailwindcss in postCSs.config.js, so this seems confusing.
| "@rspress/plugin-preview": "^1.44.0", | ||
| "@tailwindcss/postcss": "^4.1.11", | ||
| "@types/node": "^18.11.17", | ||
| "autoprefixer": "^10.4.22", |
There was a problem hiding this comment.
The autoprefix feature has been built in since tailwindcss v4. In addition, rspress is based on ByteDance's Rspack compiler, and the lightningcss used by Rspack also supports this function. This seems redundant.
| @@ -0,0 +1,40 @@ | |||
| @import "tailwindcss"; | |||
There was a problem hiding this comment.
I prefer to implement this pattern for our main project (./src) code rather than for the documentation site.
2 participants
No description provided.