You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Handle postcss throwing when parsing more complex files (#1043)
Fixes: #1033Fixes: #1034Fixes: #1035Fixes: #1036Fixes: #1037Fixes: #1038Fixes: #1039Fixes: #1040Fixes: #1041Fixes: #1042
Fixes: tailwindlabs/tailwindcss#14274
When we worked on #1030, we added a new `postcss` run inside the project
locator. Unfortunately this can crash (e.g. when non standard CSS
features are discovered like those in a `.sass` or `.scss` file) which
currently breaks the whole project locator step, making the extension
not work anymore as soon as such a file is detected.
The short term fix here is to handle this error. In the very future we
have to replace this postcss step anyways because now that Tailwind v4
supports plugins and JS config files, we need to be able to execute the
config to get the proper sources.
## Before
<img width="659" alt="before"
src="https://github.com/user-attachments/assets/8f86e70d-66c2-40a1-ba97-9f4b9b018c94">
## After
<img width="656" alt="after"
src="https://github.com/user-attachments/assets/bfd17b72-c748-4ea9-b73d-86c444cda16a">
Copy file name to clipboardExpand all lines: packages/vscode-tailwindcss/CHANGELOG.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## Prerelease
4
4
5
-
-Nothing yet!
5
+
-Fix an issue that caused the language server for any project with a non-standard CSS file to crash ([#1030](https://github.com/tailwindlabs/tailwindcss-intellisense/pull/1030))
0 commit comments