-
Notifications
You must be signed in to change notification settings - Fork 12k
feat(@angular-devkit/build-angular): detect and use tailwindcss in projects #19935
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
Merged
Conversation
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
alan-agius4
reviewed
Feb 2, 2021
packages/angular_devkit/build_angular/src/webpack/configs/styles.ts
Outdated
Show resolved
Hide resolved
alan-agius4
reviewed
Feb 2, 2021
packages/angular_devkit/build_angular/src/webpack/configs/styles.ts
Outdated
Show resolved
Hide resolved
alan-agius4
reviewed
Feb 2, 2021
packages/angular_devkit/build_angular/src/webpack/configs/styles.ts
Outdated
Show resolved
Hide resolved
alan-agius4
reviewed
Feb 2, 2021
packages/angular_devkit/build_angular/src/webpack/configs/styles.ts
Outdated
Show resolved
Hide resolved
3a59e05
to
03ac465
Compare
…ojects This feature adds detection of the `tailwindcss` package (https://tailwindcss.com) and provides a mechanism to automatically include support. To enable tailwindcss for a project, two actions must be taken: 1) Install `tailwindcss` into the Angular workspace (`npm install -D tailwindcss`/`yarn add -D tailwindcss`) 2) Create a tailwindcss configuration file (`tailwind.config.js`) in either the workspace root or the project root. A configuration file in the project root takes precedence over one in the workspace root. When both conditions are met, the Angular CLI will initialize and integrate tailwindcss into the stylesheet build pipeline.
03ac465
to
8f0c1c5
Compare
alan-agius4
approved these changes
Feb 3, 2021
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.
LGTM
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
action: merge
The PR is ready for merge by the caretaker
target: minor
This PR is targeted for the next minor release
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.
This feature adds detection of the
tailwindcss
package (https://tailwindcss.com) and provides a mechanism to automatically include support. To enable tailwindcss for a project, two actions must be taken:tailwindcss
into the Angular workspace (npm install -D tailwindcss
/yarn add -D tailwindcss
)tailwind.config.js
) in either the workspace root or the project root. A configuration file in the project root takes precedence over one in the workspace root.When both conditions are met, the Angular CLI will initialize and integrate Tailwind CSS into the stylesheet build pipeline.
Both global and component stylesheets will be processed when enabled. For component stylesheets, disabling view encapsulation is recommended due to the global nature of Tailwind CSS.