Angular teams lack supported runtime and compiler configuration hooks
Angular developers report needing runtime configuration and custom TypeScript transformers, but rely on separate implementations or brittle build hacks. The transformer gap also affects library builds, where ng-packagr reportedly does not expose the needed option. A request for choosing a tsconfig path in ncc is adjacent evidence of build-tool configuration friction, but the clearest product opportunity is Angular-focused.
For angular application and library developers. Mentioned from Apr 2019 to Oct 2024 on GitHub.
4 different people described this problem in 3 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 6.0/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
The current methods to add custom transformers to angular are all brittle hacks. It's not something you want to add to a large enterprise app. Besides, none of these hacks work with angular libraries because ng-packagr doesn't even expose the transformers array
I would also love to have this in the angular CLI. Just found a blog explaining how you could already do this using ngx-build-plus: https://medium.com/joolsoftware/custom-typescript-transformers-with-angular-cli-7f4150797e05
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks