Upgrade to Angular 14

[mshima]

Overview of the feature request

Angular 14 has been released.

The most significant change is typed forms.
As part of this migration, we should migrate away from FormBuilder.

• update build config
• migrate to typed form

We are missing libs to support it, but we can start migration.

Dependencies:

• jest@28
• @angular-builders/* (Angular 14 just-jeb/angular-builders#1219)
• @angular-eslint/eslint-plugin (feat!: update to Angular v14 angular-eslint/angular-eslint#1004)
• @fortawesome/angular-fontawesome (v0.11.0)
• @ngx-translate/* (peer >= 13)
• @ng-bootstrap/ng-bootstrap (Add support to angular 14 ng-bootstrap/ng-bootstrap#4340)
• ngx-cookie-service (v14.0.0)
• ngx-infinite-scroll (Angular 14 orizens/ngx-infinite-scroll#404)
• ngx-webstorage

Motivation for or Use Case

Keep updated

Related issues or PR

#18586

• Checking this box is mandatory (this is just to show you read everything)

[Tcharl]

Deserves a bounty, doesn't it?

[DanielFran]

Adding a bug bounty, it is a lot of work

[ari62]

apologies if this isn't the correct place to ask, but will we be able to upgrade our angular version easily via a jhipster or angular command line command? thank you

[Tcharl]

Hi @ari62 , it's in the doc here: https://www.jhipster.tech/upgrading-an-application/

[ksilz]

@Tcharl, that page doesn't mention Angular (or React or Vue, for that matter). Here's what step 8 in the "Step-by-step explanation of the upgrade process" says: "Re-generate the application using the jhipster --force --with-entities command."

I think this means there's no use of the Angular upgrade command as the Angular application is re-created from scratch. The resulting new Angular application is then combined with the existing version of that Angular application through Git merge. Correct?

[ksilz]

@ari62 Please see my previous comment if you haven't done so. @Tcharl agrees with it.