Reference imports should not generate utilities#15307
Merged
philipp-spiess merged 1 commit intoDec 5, 2024
Merged
Conversation
philipp-spiess
force-pushed
the
fix/reference-import-should-not-create-utilities
branch
2 times, most recently
from
051fdba to
204b444
Compare
philipp-spiess
force-pushed
the
fix/reference-import-should-not-create-utilities
branch
from
204b444 to
22aeddf
Compare
RobinMalfait
approved these changes
Dec 5, 2024
philipp-spiess
deleted the
fix/reference-import-should-not-create-utilities
branch
|
It happens even if you do not use |
Contributor
Author
|
@madmoizo Hey! your issue seems unrelated to the |
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
3 participants
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.
We noticed an issue where the new
@import "…" referencesyntax was not throwing away@tailwinddeclarations, effectively causing you to create utility classes whenever you used this feature.This is especially noticed in setups with very strict compilers like Svelte.
Test Plan
Before
After