feat(angular): add tailwind support for buildable libraries #7961
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.
Current Behavior
When building a buildable library, Tailwind directives (e.g. @apply) are not processed because
ng-packagr
doesn't support Tailwind out of the box and it doesn't allow either to provide our own PostCSS configuration.For more details see #6924 (comment).
Expected Behavior
Building a buildable library that uses Tailwind should correctly process any directive found in the stylesheets.
Given
ng-packagr
doesn't support Tailwind natively (as the@angular-devkit/build-angular:browser
does) and it doesn't allow us to specify custom PostCSS config, we need to provide a different implementation that does support Tailwind natively. This provides a similar experience to Angular applications where Tailwind just works.Related Issue(s)
Fixes #6924
Fixes #7965