-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to load custom PostCSS plugins #32
Add ability to load custom PostCSS plugins #32
Conversation
The getPostCSSConfiguration function was not blocking therefore the gulp-postcss instance was called before the config was loaded. This caused gulp-postcss to search for the config itself and throw an error that we did not catch when the user did not have a config.
async function cssCompile({src, dest, minified = true, browserSync = false}) { | ||
const {plugins, options = {}} = await getPostCSSConfiguration(minified); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found the little culprit..
The function that loads the PostCSS config wasn't called in a blocking way so it continued and tried to initiate gulp-postcss before actually getting the PostCSS config therefore gulp-postcss threw an error that I didin't handle.
Now that its blocking there is always a config available. Either the config from the user or the default one we provide.
No description provided.