-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
docs: move to tailwind 4 w/ vite #6168
New issue
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
Conversation
|
Important Review skippedMore than 25% of the files skipped due to max files limit. The review is being skipped to prevent a low-quality review. 193 files out of 300 files are above the max files limit of 100. Please upgrade to Pro plan to get higher limits. You can disable this status message by setting the ✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
View your CI Pipeline Execution ↗ for commit 528995e
☁️ Nx Cloud last updated this comment at |
7a3a8e3 to
98fb3be
Compare
Prev. we made sure tailwind used postcss everywhere:
That's because it's only now, per tailwind 4.1.18 that there's full support for Env API
This PR moves to the
@tailwindcss/vitefor all but the examples/e2e for rspack/webpack/esbuildSo for vite usage, this is fewer dependencies, less config files, and better perf than postcss as mentioned here: