Fix Tailwind config file resolution when Prettier config file is not present#62
Merged
Fix Tailwind config file resolution when Prettier config file is not present#62
Conversation
This was referenced Feb 24, 2022
bronisMateusz
pushed a commit
to bronisMateusz/prettier-plugin-tailwindcss-drupal
that referenced
this pull request
Apr 16, 2025
…present (tailwindlabs#62) * Update config file resolution * Add "no prettier config" test case
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR fixes Tailwind config file resolution when no Prettier config file is present. Now, when the
tailwindConfigoption is not provided the plugin will search up the directory hierarchy from a "base" directory, looking for a config file. The base directory is determined in this order:options.filepath), if providedprocess.cwd())Additionally, the
VSCODE_CWDenvironment variable is no longer used because its value is not necessarily equal to the directory that is currently open in VS Code, as originally thought.