Apparently I didn't add the dependencies in a correct way but I am not sure what's the correct way. What I have done is cd adev && pnpm install -D tailwindcss@3 postcss autoprefixer. Please let me know how to fix the lockfile issue.

Deployed adev-preview for c1bb70a to: https://ng-dev-previews-fw--pr-angular-angular-63583-adev-prev-fdy17wh7.web.app

Note: As new commits are pushed to this pull request, this link is updated after the preview is rebuilt.

Are we sure we want tailwind without actually using it all over the place?

The main purpose is providing code examples for developers to use in their Tailwind CSS based project. Using it across adev is a different story that requires some clean up for Tailwind preflight(base styles) to work, but certainly doable.

I am curious if we see a large diff in the sizes of out generated outputs, I don't know that we have dead code elimination in CSS

For now it added a few lines for css variables. Tailwind only adds new styles when utility classes are used in templates that it parses, so there should be no dead css code in theory.

@ok7sai, this require a rebase and it doesn't apply cleanly on the patch branch.

Rebase done 👍

I see that you just added the action: merge label, but the following checks are still failing:
failure conflicts with base branch "main"

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken main, please try rebasing to main and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

@ok7sai Looks like this needs a rebase and to resolve conflicts. These two files are likely to have conflicts pretty quickly. So definitely keep an eye on it until it merges.

This PR was merged into the repository. The changes were merged into the following branches:

• main: d9483fa