Upgrade to Angular 17

[mraible]

Overview of the issue

Upgrade and release before January, ideally.

• [x] update dependencies https://github.com/jhipster/generator-jhipster/pull/24254
• [x] switch to new declarative control flow https://github.com/jhipster/generator-jhipster/pull/24316
• [ ] ~switch to esbuild for non microfrontends~
• [x] convert application root to standalone https://github.com/jhipster/generator-jhipster/pull/24398
• [ ] ~replace webpack eslint plugin with ng lint~

Motivation for or Use Case

https://www.youtube.com/watch?v=Wq6GpTZ7AX0

[dinu0000]

Will work on it when Angular 17 is released 😊

[mraible]

You should be able to start on it with the RC candidates before the release. Angular CLI has 17.0.0-rc.3 available, and the rest of the libraries should be available in 17.0.0-rc.2.

https://github.com/angular/angular/releases

[mraible]

This is a good article detailing what's new in Angular 17: https://www.angulararchitects.io/en/blog/whats-new-in-angular-17/

[mrts]

Should we migrate to built-in control flow, signals and other "Angular renaissance" goodies or is this planned separately?

[mraible]

@mrts We already migrated to @if and @for for control flow. We haven't done anything with signals.

[mshima]

I have looked at build-esbuild status and I don't think we can migrate to it right now.

• custom build api support is not stable.
• angular-builders doesn't provide a custom builder helper yet.
• we need custom builder of i18n support.

I will remove it from tasks.

[Ahrovan]

@mraible how to use --no-standalone for angular project? need this

[mraible]

We currently don't provide support for this.

[mshima]

This is complete.

@mraible implemented new control flow migration. @qmonmert signals migration had a different bounty https://github.com/jhipster/generator-jhipster/pull/25074. I've implemented the standalone migration and signals migration at https://github.com/jhipster/generator-jhipster/pull/25120, https://github.com/jhipster/generator-jhipster/pull/25068, https://github.com/jhipster/generator-jhipster/pull/25047 and others.

I think this bounty can be split by @mraible and me.

[mraible]

@DanielFran Half of the bounty claimed at https://opencollective.com/generator-jhipster/expenses/203504.

[DanielFran]

@mraible approved

[mshima]

@DanielFran half bounty claimed https://opencollective.com/generator-jhipster/expenses/211708.

[DanielFran]

@mshima approved