Angular teams patch CLI gaps with fragile build-workflow workarounds
Teams with multi-project Angular workspaces run into awkward or missing support for custom build steps, code generation, environment configuration, and faster incremental or watch builds. They patch workflows with scripts, webpack overrides, or fragile custom code, and those workarounds do not cover every gap. The reports span several Angular CLI capabilities, so a useful product should focus on a narrow, recurring workflow rather than promise to solve them all.
For angular teams maintaining multi-project workspaces. Mentioned from Dec 2017 to Oct 2024 on GitHub.
12 different people described this problem in 10 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 6.0/10
- Frequency
- 9.3/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I have a workspace with a couple of core libraries and some addons that depend on them. Here are my cases where I need hooks:
It would be ideal if ng serve is able to run codegen. And then a way to define the dependencies of codegen so Angular CLI knows when to run it
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 5 places to find your first customers
- 10 more quotes from people who have this problem
- Current workarounds, existing solutions and risks