ng-zorro-antd VS core

Ant Design: A solid option that is been used by a lot of heavy hitters, such as Tencent, Baidu, AliBaba, and more. Supports all modern browsers, SSR, esm, and even Electron. Has also community implementations for Angular, Vue, and more. Does use CSS-in-JS, so expect runtime overhead as well as AntD ways of doing things.

I've been using ng-zorro on my current project (https://ng.ant.design/)

Fortunately, antd does have an angular counterpart - ng-zorro-antd. Documentation @ https://ng.ant.design/

I'm currently working with Ant Design. It doesn't have a lot of advanced components, but its quite good. Community is still growing, so you won't be getting a lot of help online.

This is how @angular/material works but they use bazel so it is hard to replicate. Ng-zorro does it kind of you can apply their logic to your stucture. https://github.com/NG-ZORRO/ng-zorro-antd/tree/master/components

NG ZORRO - An enterprise-class UI components based on Ant Design and Angular.

NG Zorro

Github Stars: 6800+ Weekly npm downloads: 33,000+ Latest update: 7.5.1

Some libraries support ways to handle missing translations (e.g., TranslocoMissingHandler from Transloco or MissingTranslationHandler   from ngx-translate). So that's a way to find out any missing translations, but that's quite manual because you have to go over every part of the served application.

ngx-translate

It was rather painless. We are using ngx-translate which seems dead at this point but works fine in 16 (seems to have gotten a recent commit).

The problem with Angular 15 was the Ivy engine. And it wasn't fixed, maybe you're not affected. https://github.com/ngx-translate/core/issues/1185

He talks about it more here: https://github.com/ngx-translate/core/issues/783

Ngx-translate is not updated anymore. Latest version is a year old. It's still not abandoned but it seems like the developer moved on to work on Angular i18n.

Just to refer to the original docs: https://github.com/ngx-translate/core

One of the common pitfalls when using i18n are large translation files size and inability to split them in order to hide parts of your application from prying eyes. Some solutions like Angular built-in implementation are really powerful and SEO compatible but require a lot of preparation and do not support switching languages on the fly in development mode (which was causing troubles at least in version 9); other solutions like ngx-translate require you to install several packages and still don’t support splitting up a single language.