-
Notifications
You must be signed in to change notification settings - Fork 11.9k
feat(@angular-devkit/build-angular): partial custom postcss config support #30592
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
Conversation
...onfiguration support The `browser` builder now supports providing a custom postcss configuration similar to the functionality available in the `@angular/build:application` builder. A postcss configuration file named either `postcss.config.json` or `.postcssrc.json` will be discovered in order from the project root or workspace root. Only plugins can be configured via the file. All other fields will be ignored. Additionally the plugins will be placed after any internal build system plugins but before `autoprefixer`. When using a custom postcss configuration, the automatic tailwind integration will be disabled. The Tailwind postcss plugin should be added to the configuration file in this scenario. Co-Authored-By: Jan Martin <jankrems@google.com>
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.
This require.resolve was added to the original code to ensure the plugins are resolved relative to the project.
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
The
browserbuilder now supports providing a custom postcss configuration similar to the functionality available in the@angular/build:applicationbuilder. A postcss configuration file named eitherpostcss.config.jsonor.postcssrc.jsonwill be discovered in order from the project root or workspace root. Only plugins can be configured via the file. All other fields will be ignored. Additionally the plugins will be placed after any internal build system plugins but beforeautoprefixer. When using a custom postcss configuration, the automatic tailwind integration will be disabled. The Tailwind postcss plugin should be added to the configuration file in this scenario.