Generator-jhipster: Upgrade to webpack 5

[mraible]

Overview of the feature request

Released today! https://twitter.com/thelarkinn/status/1315062117221851136?s=21

Motivation for or Use Case

It will make micro frontends easier to implement.

Related issues or PR

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

[mraible]

I don't think this will be easy, so I'm assigning a bug bounty to this. I can increase the amount if requested.

[mshima]

I will be working on this.

[mshima]

@mraible @angular/cli@10 will not provide support for webpack@5 https://github.com/angular/angular-cli/issues/17555#issuecomment-701359679.
@angular/cli@10 has a peer dependency on webpack@4, so it will conflict with https://github.com/jhipster/generator-jhipster/issues/12747.

At angular front, webpack@5 will happen by default with angular@11 only.
Don't have time to look at others frameworks now.

[gmarziou]

Once #10624 is complete, this would come "for free"

[artemis-bot]

@mshima is there any progress on this issue so far? We would also gladly transition to Webpack 5 with our jhipster application, as soon as Angular 11 is available, which seems to be in the near future. RC1 is already available.

[mshima]

@artemis-bot there is nothing we can do for angular in our side right now.
We need to wait webpack 5 support from dependencies like https://www.npmjs.com/package/@angular-builders/custom-webpack.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity.
Our core developers tend to be more verbose on denying. If there is no negative comment, possibly this feature will be accepted.
We are accepting PRs :smiley:.
Comment or this will be closed in 7 days

[pascalgrimaud]

still in todo list

[krusche]

any news here?