-
Notifications
You must be signed in to change notification settings - Fork 215
[pre-release] intellisense broken since 0.13.29 #1035
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
Comments
v0.12.7 also not fine (same error), I use with my Angular project which quite a lot of folder of component. But everything is fine with version 0.12.6 |
v0.12.7 is not working here too. After downgrading to 0.12.6 it worked again. |
Not working for me either... 0.12.6 does though... I'm not seeing 0.13.28 in vscode... |
Same here, same error. Reverting to |
Same here, 0.12.7 is broken |
If anyone doesn't yet know how to revert on VSCode, to save you a google search: Go to the VSCode Extensions list, search for/find "Tailwind CSS Intellisense", right click the tile and select "Install Specific Version" |
Can confirm, 12.7 is borken. I lost one whole day trying to fix thinking someone in the team introduced something that broke the extension. Hope this will be fixed soon. |
It works |
Thank you for this thread. I have been struggling to find a fix for days. Reverting to Tailwind CSS IntelliSense version v0.12.6 has worked. |
Hey @joy-yu! Thanks for reporting this and sorry for the troubles! We just released v0.12.8 of the VS Code extension with a fix that resolves this issue. If you still have issues, please let us know! |
🥳 🥳 🥳 🥳 🥳 🥳 🥳 🥳 🥳 🥳 Thanks for the great work folks! Much appreciated! |
What version of VS Code are you using?
1.92.2
What version of Tailwind CSS IntelliSense are you using?
0.13.31
What version of Tailwind CSS are you using?
3.4.10
plugin output
Describe your issue
Everything is fine with version 0.13.28.
Does pre-release version have destructive updates that make it incompatible with tailwind 3.x?
The text was updated successfully, but these errors were encountered: