Skip to content

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
merged 1 commit into from
Feb 3, 2021

Conversation

clydin
Copy link
Member

@clydin clydin commented Feb 2, 2021

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 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.

@google-cla google-cla bot added the cla: yes label Feb 2, 2021
@clydin clydin force-pushed the tailwind-integration branch 2 times, most recently from 3a59e05 to 03ac465 Compare February 2, 2021 19:21
…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.
@clydin clydin force-pushed the tailwind-integration branch from 03ac465 to 8f0c1c5 Compare February 2, 2021 20:33
@clydin clydin marked this pull request as ready for review February 2, 2021 20:37
Copy link
Collaborator

@alan-agius4 alan-agius4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release labels Feb 3, 2021
@alan-agius4 alan-agius4 merged commit 73b4098 into angular:master Feb 3, 2021
@clydin clydin deleted the tailwind-integration branch February 3, 2021 10:59
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Mar 13, 2021
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants