-
Notifications
You must be signed in to change notification settings - Fork 12k
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
feat: support tailwind v4 #28939
base: main
Are you sure you want to change the base?
feat: support tailwind v4 #28939
Conversation
packages/angular_devkit/build_angular/src/tools/webpack/configs/styles.ts
Show resolved
Hide resolved
would be good to have same support for esbuild builder too, not only for webpack |
Agreed, I found what seems to be the correct place here https://github.com/angular/angular-cli/pull/28939/files#diff-c31d390b8683db112fcc30e2ee984d893bdce6bd8e6d7d70c43ecc410a626a3dR489 |
The |
@clydin tailwind v4 is getting released next week, it is better have support from day 1 |
Also clears up the todo
Can't wait to get this feature |
If you are interested in updating to or trying out Tailwind v4, ensure the project is using the |
The largest change in Tailwind v4 is the extra speed from their new build system, which we can't fully appreciate with postcss mandated. I'd say it's essential this PR, or a following one, allows us to use tailwindcss without postcss |
PR Checklist
Please check to confirm your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The current integration if for tailwind V3 only.
Issue Number: #28938
What is the new behavior?
Detect if tailwind v4 is used as indicated by the presence of the
@tailwindcss/postcss
package. If so, check that alsotailwindcss
is installed. If both are present, Add the tailwind postCSS plugin.Does this PR introduce a breaking change?
Other information