-
-
Notifications
You must be signed in to change notification settings - Fork 253
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
Tailwind V4 support #1328
Comments
Easiest fix would be to add |
The issue is that it enforces the file name. So, it won't work on existing projects that don't use this name. |
No, it won't, but an alternative is to always scan all CSS files for the magic string, which will worsen performance. There's kind of no easy solution here thanks to their decision to drop a config file. |
What about scanning all css files once at startup to check for the presence of specific patterns ? |
Yep. I've seen that. They seem to have lots of issues themselves with projects not being recognized https://github.com/tailwindlabs/tailwindcss-intellisense/issues And this could happen in larger projects tailwindlabs/tailwindcss-intellisense#1109 |
Would need some help from someone more experienced in the Neovim and Lua ecosystem 🙂 |
Yeah, it looks like it is a big design flaw on their side. |
Another option is to scan |
Is your feature related to a problem?
Tailwindcss V4 dropped few hours ago. And with the new major release, the way configuration are handled completely, moving from a js file to a css-firsr configuration. Which means the tailwindcss pack doesn't work anymore since it doesn't detect any JS configuration.
Describe the new feature
The tailwindcss pack needs some tweaking in order to make it work again.
Additional context
No response
The text was updated successfully, but these errors were encountered: