Choosing a component framework is always a crucial step when you're about to define the technology stack for a new product. It's never, in my experience, an easy task.
The guidelines for the choice I always suggest to follow as a software architect are more or less the following:
a) is the framework supported by any software company ? How much is the support (if any) ?
b) is the community behind the framework thriving ? How often are new versions released ?
c) how many components does the framework offer, and given their features, how much do they fill your project needs ? In other word, could you use components out-of-the box or do you need to undergo an (heavy) customization ?
d) in web frameworks, look carefully which features offers the 'data table' (whatever is its name in the framework) component. If there's no datatable - dump it and choose another one. Datatable is generally speaking the most challenging component: does it offer out of the box sorting column, re-arranging columns, filtering, grouping, sorting...
e) when you have a bunch of candidates, build a proof - of - concept project whenever possible, measuring the global effort to get the project done.
Unluckily, I've no a great direct experience with Angular. When we evaluated at work which web fx to adopt for a customer that required to use JSF for its own reasons, we ended to choose Prime JSF. We found it very complete, and you need not to pay for use it.
Personally, as a developer, I'd give Prime NG a try, but mine is an idea more than an advice.
Good luck !