Hotfix: Tailwind is not included in production builds #3
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
Mafrans
changed the title
|
@txfs19260817 as you are the original author of #1 I'd like to hear your opinion on this solution. |
|
vitejs/vite#5796 has been merged and the decision not to support importing preprocessed CSS documents has been made, this solution will therefore be merged until there is support for a more elegant one. |
Closed
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.
Until importing preprocessed CSS documents as URLs is supported in Vite (see vitejs/vite#5796) it is not possible for us to directly define which documents should be loaded into web components. An alternative is to load a CSS document directly into the head and simply clone it into each web component.
Fixes #2, also probably acts as a better solution than #1.