Handle style exports condition when processing @imports
#934
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
style exports field when processing @importsstyle exports condition when processing @imports
e148870 to
13ec5d0
Compare
629d102 to
9e86bc4
Compare
.../tailwindcss-language-server/tests/fixtures/v4/workspaces/packages/style-export/package.json
Show resolved
Hide resolved
RobinMalfait
approved these changes
Mar 26, 2024
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.
If you
@import "some-package"we weren't handling thestyleexport condition. This isn't handled bypostcss-import(it doesn't support reading fromexportsat all because theresolvepackage doesn't). So here we pass a customresolve()function to handle this situation.Fixes #933