Add support for .mts and .cts config files #1025
Merged
Conversation
This file contains 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
ErlendS
changed the title
ErlendS
changed the title
thecrypticace
approved these changes
Sep 4, 2024
|
Thanks! Will get a release out with this soon — appreciate it! |
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.
Related to tailwindlabs/tailwindcss#13940
Now that tailwind supports
.ctsand.mtsfiles, tailwindcss-intellisense should also look for them.Added test where I thought it was appropriate. Note - v4 tests fail for me (but they do in the master branch has well)
Context: I recently upgraded to node v22 in my private project and noticed some warnings that lead me to this tailwind PR. I tested switching tailwind.config to be .mts and noticed intellisense had stopped working.
Decided to try to help out by creating a PR that adds support for .cts and .mts files now that tailwind supports them.