Do not export CSS as string when output is set to a file path.#6
Open
ahoereth wants to merge 1 commit into
Open
Do not export CSS as string when output is set to a file path.#6ahoereth wants to merge 1 commit into
ahoereth wants to merge 1 commit into
Conversation
Owner
|
Can not export css as string if the insert option set to be true. |
|
👍 for something like this. |
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.
Adds the possibility to set
exporttotruewhen it is desired to export the generated CSS as string. This is mostly undesirable because most users will extract all the styles to a single css bundle file. Currently the JS bundle blows up in size because it always includes all the CSS styles no matter which options are set.