Angular developers work around gaps in styling components and directives
Angular developers report friction applying styles and classes to hosts and directives, controlling CSS precedence, and getting editor support for inline preprocessors. The workarounds in these reports include wrapper elements, decorator or parent-template changes, a hacky component to load directive styles, and `!important` utilities. The signals point to several related but distinct gaps, so a focused tool is more realistic than one fix for all of them.
For angular application developers. Mentioned from Sep 2017 to Feb 2025 on GitHub.
4 different people described this problem in 4 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 5.5/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Right now I'm having to resort to marking all Tailwind utilities as !important just so they can take precedence when used on Angular Material components
For now I am thinking of adding a fake component to the same module as the directives and having the style for that component use ViewEncapsulation.None and have it's scss file import all the directive scss files. It will be a total hack, but should get the styles into any apps that use the module
Build brief
See what to build and who will buy it
- 3 product ideas with the smallest useful version and pricing
- 3 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks