Add confirmation for overwriting postcss config in tailwindcss and bt-postcss bundled configurations #317
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.
This is a 🙋 feature or enhancement.
The
tailwindcss
andbt-postcss
bundled configurations overwrite thepostcss.config.js
and the only place this is documented is on the website.This PR adds a confirmation that informs the user that the
postcss.config.js
will be overwritten and asks if they would like to proceed.Any confusion with running these two configurations one after the other should hopefully be prevented with this warning.
One area we should improve in the future is perhaps silence this warning when the config is invoked as part of
bridgetown new
but for now I reckon this should be good enough.Closes #315