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

[Bug]: PostCss problem with tailwind 4.0 #1023

Open
2 tasks
savasturkoglu1 opened this issue Jan 29, 2025 · 11 comments
Open
2 tasks

[Bug]: PostCss problem with tailwind 4.0 #1023

savasturkoglu1 opened this issue Jan 29, 2025 · 11 comments
Labels
bug Something isn't working

Comments

@savasturkoglu1
Copy link

Reproduction

We are experiencing a problem with the post member sound when installing with tailwind 4.0, I think it is not compatible with this version.

Describe the bug

We are experiencing a problem with the post member sound when installing with tailwind 4.0, I think it is not compatible with this version.

System Info

We are experiencing a problem with the post member sound when installing with tailwind 4.0, I think it is not compatible with this version.

Contributes

  • I am willing to submit a PR to fix this issue
  • I am willing to submit a PR with failing tests
@savasturkoglu1 savasturkoglu1 added the bug Something isn't working label Jan 29, 2025
@almarzn
Copy link

almarzn commented Jan 30, 2025

I have found that removing shadcn nuxt plugin fixed this issue. Although I had many issues with my styles after. Although you will have to enable auto import for ui folder

@bartblokhuis
Copy link

Just had the same issue.

The easiest fix for now would be to use tailwind 3
You can install it using

npm install -D tailwindcss@3

@mccombs
Copy link

mccombs commented Jan 30, 2025

Just had the same issue.

The easiest fix for now would be to use tailwind 3 You can install it using

npm install -D tailwindcss@3

Can confirm this works. Looking forward to support for Tailwind 4...

@Flinty916
Copy link

+1 to this problem, Tailwind 4 support would be very nice to see!

@savasturkoglu1
Copy link
Author

Yes I can use tailwind3 without any problem, as @Flinty916 said Tailwind 4 support would be very nice to see!

@florivdg
Copy link

florivdg commented Feb 3, 2025

For me importing the JS config file within the main CSS file works, too:

@import "tailwindcss";

@config "../../tailwind.config.js";

See https://tailwindcss.com/docs/upgrade-guide#using-a-javascript-config-file

@han1548772930
Copy link

shadcn-ui has a new version
https://github.com/shadcn-ui/ui/tree/main/apps/v4

@orenmizr
Copy link

orenmizr commented Feb 5, 2025

is it me or it feels like this project lost traction.... started strong and ended up like every react port. it is hard to bet on vue frameworks lately.

@sadeghbarati
Copy link
Collaborator

sadeghbarati commented Feb 5, 2025

is it me or it feels like this project lost traction.... started strong and ended up like every react port. it is hard to bet on vue frameworks lately.

Yes, I kinda feel the same, but everyone has a life

When you get the people's support, you can work on the project
Mainly pointing to Zernonia, people should support him more so he could work on OS projects

@sj0n
Copy link

sj0n commented Feb 10, 2025

I got tailwindv4 to work with the current package version.

  1. Uninstall shadcn-vue & @nuxtjs/tailwindcss modules from package.json and remove it from nuxt config.
  2. Run the migratation script from tailwind if you haven't.
  3. Install @tailwindcss/vite and add it to nuxt config under the vite.plugins option.

Everything should be working now.

@hdwebpros
Copy link

is it me or it feels like this project lost traction.... started strong and ended up like every react port. it is hard to bet on vue frameworks lately.

Two things can be true at the same time.

  • Yes, maybe this project has lost traction. It's one of those things where I wish I had the skillset to contribute more, I just don't.
  • I wouldn't go as far as saying it's hard to bet on Vue frameworks -- at least with Nuxt. There were only two JS frameworks that grew last year in the amount that developers love working with them, I believe they were Astro and Nuxt. Nuxt is solid, we've used it for a ton of client sites and some complex web apps too.

We will be trying this for two new projects soon, I hope the install process plays a bit nicer by then :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests