Update to angular 17 and update implementation to new angular standards.

[mshima]

• drop ngx-webstorage package. It usually takes a few weeks to update and its usage is trivial.
• update to angular 17
• convert components to standalone components.
• Change to new control flow syntax #998

[mraible]

I'm not sure we should migrate to standalone components for Ionic. I spent some time yesterday trying to migrate @oktadev/schematics to use standalone components for Ionic. I found that I had to import so many components in the tabs page that it was exhausting, and I decided it wasn't work it. https://github.com/oktadev/schematics/pull/1210/files#diff-9c6765d50519f26b8b3344fe553a875ef6d3f21e10215b11291f56f3d39fecc0

[mshima]

At jhipster we have a single @NgModules for common components.
https://github.com/jhipster/generator-jhipster/blob/main/generators/angular/templates/src/main/webapp/app/shared/shared.module.ts.ejs

[mraible]

@mshima I think it'd be good to release a version that works with Node 18 and JHipster 8, then address standalone components afterward. What do you think?

[mshima]

@mraible sure we should not block releases for small improvements.
We need a new release for micronaut and quarkus too if you have permission.

[mraible]

@mshima I agree that we should release new JHipster 8 blueprints for Micronaut and Quakus. They both have publish pipelines like this repo, so as soon as we create a new release in GitHub, it publishes it to npmjs.com.

[mraible]

The Micronaut blueprint is currently blocked by jhipster/generator-jhipster-micronaut#295 and the Quarkus blueprint is blocked by jhipster/generator-jhipster-quarkus#306.

[mshima]

The Micronaut blueprint is currently blocked by jhipster/generator-jhipster-micronaut#295 and the Quarkus blueprint is blocked by [jhipster/generator-jhipster-quarkus#306]

I think we should release based on micronaut v3 before moving to v4.

(jhipster/generator-jhipster-quarkus#306).

Should be fixed by jhipster/generator-jhipster-quarkus#308

[mraible]

I think we should release based on micronaut v3 before moving to v4.

I'm fine with that. Is there anything we need to do for that or is it ready to release? If it's ready, I can do it today.

[mshima]

I think we should release based on micronaut v3 before moving to v4.

I'm fine with that. Is there anything we need to do for that or is it ready to release? If it's ready, I can do it today.

I think you can go ahead.
This week I will do only limited work on mobile.

[mraible]

It looks like Micronaut 3 was already released in the v2.0.0.

[mshima]

Yes, but with angular 14 and vue 2.

[mraible]

So you're saying we should release a v2.1.0 that uses Micronaut 3 and JHipster 8?

[mshima]

Release v3.0.0 which uses micronaut 3 and JHipster v8.0.0

• drops support for node v12, v14 and v16.
• add support for node v18 and v20 (currently broken)
• includes angular 16, vue 3.2 and java 7 by default.

For micronaut v4 we can release blueprint v3.1.0 or v4.0.0.
Ideally we should update to jhipster v8.1.0, but since it’s just create a tag we should do releases more often.

[mraible]

I'm not sure we need to release a new version with Micronaut 3. I get the feeling that people won't use it because they'll want to use the latest version of Micronaut. JHipster is used to start new projects, and people want to use the latest versions when they start new projects.

According to npmjs.com, the Micronaut blueprint had ~200 downloads when 2.0.0 was released but seems to average < 20 per week since then.