Fixed issue where postcss plugins weren't being applied #513
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
|
looking forward to |
This was
linked to
issues
May 26, 2023
dilanx
approved these changes
May 26, 2023
|
@dilanx Hi :) |
|
@stevenewald @dilanx |
I resolved this by the |
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.
Previously, loader.options.postcssOptions.plugins was assigned to () => postcssPlugins, which was incorrect. It should instead directly assign the value of the plugins array.
This PR should fix the issues mentioned in #505 and #506 - hopefully it fixes #478, but I haven't tested this.