Skip to content
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

I can't use Tailwind #37

Closed
jrobertogram opened this issue Jan 25, 2025 · 3 comments
Closed

I can't use Tailwind #37

jrobertogram opened this issue Jan 25, 2025 · 3 comments

Comments

@jrobertogram
Copy link

jrobertogram commented Jan 25, 2025

[plugin:vite:css] [postcss] It looks like you're trying to use tailwindcss directly as a PostCSS plugin. The PostCSS plugin has moved to a separate package, so to continue using Tailwind CSS with PostCSS you'll need to install @tailwindcss/postcss and update your PostCSS configuration.
at Te (C:\Users\jrobe\OneDrive\Documentos\workspace\leaf-teste\node_modules\tailwindcss\dist\lib.js:33:1740)
at LazyResult.runOnRoot (C:\Users\jrobe\OneDrive\Documentos\workspace\leaf-teste\node_modules\postcss\lib\lazy-result.js:329:16)
at LazyResult.runAsync (C:\Users\jrobe\OneDrive\Documentos\workspace\leaf-teste\node_modules\postcss\lib\lazy-result.js:258:26)
at LazyResult.async (C:\Users\jrobe\OneDrive\Documentos\workspace\leaf-teste\node_modules\postcss\lib\lazy-result.js:160:30)
at LazyResult.then (C:\Users\jrobe\OneDrive\Documentos\workspace\leaf-teste\node_modules\postcss\lib\lazy-result.js:404:17
Click outside, press Esc key, or fix the code to dismiss.
You can also disable this overlay by setting server.hmr.overlay to false in vite.config.js.

@mychidarko
Copy link
Member

Looks like Tailwind v4 being the new default broke things a bit, have limited the setup to v3 so you can use that in the mean time, but I will push out another update to set tailwind up using v4

@mychidarko
Copy link
Member

I've updated the view:install command to use v4, documentation has also been updated

@mychidarko
Copy link
Member

@jrobertogram have you been able to check the fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants