Properly restart server when detecting new Tailwind CSS v4 configs #1387
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
thecrypticace
changed the title
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.
In editors that use our language server directly (not our VSCode extension), if you start with a project with a CSS file that isn't a Tailwind CSS config then edit it we want the server to restart.
Unfortunately this was hitting an error causing the restart to fail but because of how things are set up this error isn't easily catchable (but it did get logged thankfully).
This fixes that error and turning a CSS file from a non-config into a proper Tailwind CSS v4 config should work and the server should react accordingly.