Add and document purgeCssEnabled option #20
Merged
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
lucleray
requested changes
Jun 25, 2019
Co-Authored-By: Luc <[email protected]>
Co-Authored-By: Luc <[email protected]>
|
Good suggestions, I just finished updating 👍 |
lucleray
approved these changes
Jun 25, 2019
|
Thanks! Published in |
|
I would suggest disabling it automatically in dev mode with the next major release (since it's a breaking change). |
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.
Adds
purgeCssEnabled, a new option that allows you to control whether or not PurgeCSS is enabled based on build environment (development/production and server-side/client-side). Inspired by theenabledoption from nuxt-purgecss.Super useful for developers who design in the browser using atomic CSS frameworks like Tailwind, and therefore need all CSS classes available in the development build.
nuxt-purgecssactually disables PurgeCSS for dev and server environments by default, which is my preference, but I wrote this pull request to keep PurgeCSS enabled by default so that this isn't a breaking change.