Repository navigation
fix(@schematics/angular): ignore non-workspace stylesheet entries when adding Tailwind - #34507
Merged
Merged
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the Tailwind schematic to only modify workspace source files, ensuring that external package specifiers and files within node_modules are not modified. It also adds unit tests to cover these scenarios. A review comment suggests enhancing the node_modules path check to also exclude paths starting with ./node_modules/ for robustness.
alan-agius4
requested changes
Oct 23, 2026
MeAkib
force-pushed
the
fix/tailwind-vendor-stylesheets
branch
from
October 23, 2026 17:23
b2eca96 to
9b9cda4
Compare
alan-agius4
added
the
action: cleanup
…n adding Tailwind The tailwind schematic selects the first `styles` entry ending in `.css` and appends the Tailwind import to it without checking that the entry is a file in the workspace. When the first `.css` entry is a package specifier such as `@angular/material/prebuilt-themes/azure-blue.css`, `ng add tailwindcss` fails with a file-does-not-exist exception, and when it is a path within `node_modules`, the vendor stylesheet is modified instead of a project file. Only consider entries that exist in the workspace and are not within `node_modules`, falling back to creating a dedicated `tailwind.css` otherwise. New specs reproduce both failures without this change.
alan-agius4
force-pushed
the
fix/tailwind-vendor-stylesheets
branch
from
October 27, 2026 14:27
9b9cda4 to
01c9fbf
Compare
alan-agius4
added
target: patch
Collaborator
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The tailwind schematic selects the first
stylesentry ending in.cssand appends the Tailwind import to it without checking that the entry is a file in the workspace. When the first.cssentry is a package specifier such as@angular/material/prebuilt-themes/azure-blue.css,ng add tailwindcssfails with a file-does-not-exist exception, and when it is a path withinnode_modules, the vendor stylesheet is modified instead of a project file. Only consider entries that exist in the workspace and are not withinnode_modules, falling back to creating a dedicatedtailwind.cssotherwise. New specs reproduce both failures without this change.