A client wants to go all in on angular material components (instead of bootstrap, tailwind) and material icons (instead of font awesome) for their web app (a regular CRUD web app in angular). Just wanted to check if anyone has done this before? What were your learnings? Any disadvantages or shortcomings that I should be aware of? Backstory: Their current angular app uses a random mishmash of libraries: bootstrap, material, font-awesome, prime-ng, semantic-ui, plus a bunch of other random NPM packages. It's all over the place and visually inconsistent. So they want to converge on material (which has good angular component support).

Angular is good monolith to go all in, like they want to, provided that they're willing to commit to Typescript for the long term. It is just that if app isn't going to scale up over time with lot of features getting added, Angular may just be an overkill. I'm guessing they're willing to go with it because their past experience of building frontend stack by combining libraries hasn't been great.