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
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.
PR Checklist
Please check to confirm your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
executor: @angular-devkit/build-angular:dev-server
Users can use customized postcss config, but json only, have a lot of limitions.
Issue Number: #27819
What is the new behavior?
Users can use js config file(.js, .cjs and .mjs), it not only can handle all situations of json config, but also more powerful.
And the postcss early migration guide still recommend to use js as configuration file.
Does this PR introduce a breaking change?
Not support json configuration again. Try support json or ts will increase the complexity of code bases.
Other information