We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I raised an issue about the Tailwindcss style not being effective before.
With the enthusiastic help of Vitepress team member brc-dd, I solved this problem.
But now we have encountered a very tricky problem
https://github.com/ajiho/vitepress-tdcss-with-outside-srcdir-invalid
Even if srcdir is set outside the current working directory, tailwindcss can still function properly
System: OS: Windows 10 10.0.19044 CPU: (8) x64 Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz Memory: 1.90 GB / 7.91 GB Binaries: Node: 22.11.0 - C:\Program Files\nodejs\node.EXE npm: 10.9.0 - C:\Program Files\nodejs\npm.CMD Browsers: Edge: Chromium (131.0.2903.86) Internet Explorer: 11.0.19041.3636 npmPackages: vitepress: ^1.5.0 => 1.5.0
No response
The text was updated successfully, but these errors were encountered:
I have tried to modify the content attribute of TDconfig, but neither absolute nor relative path works
Sorry, something went wrong.
@brc-dd Can you help me take a look? Thank you.
The problem has been resolved, I have decided to close it
What was the solution? Moving tailwind config to outside-src? (You can probably configure tw config path in postcss config too 👀)
No branches or pull requests
Describe the bug
I raised an issue about the Tailwindcss style not being effective before.
With the enthusiastic help of Vitepress team member brc-dd, I solved this problem.
But now we have encountered a very tricky problem
kk.2025-01-01.14-51-08.mp4
Reproduction
https://github.com/ajiho/vitepress-tdcss-with-outside-srcdir-invalid
Expected behavior
Even if srcdir is set outside the current working directory, tailwindcss can still function properly
System Info
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: