docs(v1-tailwind4): update v1 how to use tailwind 4#2160
docs(v1-tailwind4): update v1 how to use tailwind 4#2160Gao-pw wants to merge 1 commit intoweb-infra-dev:1.xfrom
Conversation
✅ Deploy Preview for rspress ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
This document seems to have not solved this problem. tinytek-io/windcraft-starter-kit#9 this is not just a change on doc; supporting Tailwind V4 is a feature with code, testing, and documentation. |
😦I will add some test cases later. I am currently a user of rspress 1.X, so I only mentioned the pr for version 1.X😢. |
|
Thanks for your supporting. If we haven't tested this usage of tw4, and whether it is working normally in Rspress, we cannot document it to recommend users to use it... Sorry If you want to continue this pr, you can add a test case to cover it and declare the document how to use tailwind v3 and how to use tailwind v4, split them to 2 parts |
|
In V2, all Rspress built-in components use BEM naming conventions and do not use Tailwind CSS internally, which avoids conflicts with Tailwind CSS classes. You can freely use Tailwind v4 or v3 without worrying about style collisions. Closing this PR due to prolonged inactivity. Thank you for your contribution! If you'd like to continue working on this, please feel free to reopen or submit a new PR based on the latest |

Summary
update rspress v1 how to use tailwind 4
Related Issue
#2158
Checklist