Handle postcss throwing when parsing more complex files #1043
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Aug 28, 2024
|
for people with that issue: Just switch to the pre-release version of the extension, worked for me. |
|
@lrungg The fix or this was already released as version 0.12.8 so it should be fine to update to the latest stable version. 🙂 |
|
Oh my god! I never thought it was a problem with Tailwind SLP! I changed four or five editors because of this problem, and I always thought there was a problem with my project! In the past three days, I removed scss files every day to try to solve this problem! 😭 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #1033
Fixes: #1034
Fixes: #1035
Fixes: #1036
Fixes: #1037
Fixes: #1038
Fixes: #1039
Fixes: #1040
Fixes: #1041
Fixes: #1042
Fixes: tailwindlabs/tailwindcss#14274
When we worked on #1030, we added a new
postcssrun inside the project locator. Unfortunately this can crash (e.g. when non standard CSS features are discovered like those in a.sassor.scssfile) 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
After