I've had a brief stint pairing this lib with Angular and server-side pagination while also trying to dance around Django's CSRF requirements on a local machine (aka two separate ‘servers’ for Angular and Django). That was a rather mixed experience, Tabulator mostly prefers convention so bending it to fit an opinionated framework like Angular is awkward. IIRC I still had to deal with data requests via Angular and from Tabulator itself. Never managed to put CSS styles for Tabulator in component styles instead of global ones.

Long story short, for Angular there are similar widgets that also happen to be more popular. I didn't end up using them, so can't say for sure, but I imagine they fit more nicely with the framework they were made for.

Also, dunno if anything changed, but six months ago Tabulator could use some fine tuning in regard to UX with pagination: if the table is scrolled to the right, on every filtering or pagination operation the position is reset to zero (but not on the table headers, notably). There's also no support for more interesting filtering like number ranges, so I'd need to whip up widgets for that myself.

And, for some reason, the lib sent two data requests every time filters were changed.