Generator-jhipster: Vue 3

[pascalgrimaud]

Overview of the feature request

Vue 3 has been released !
It would be so cool if we can have it for JHipster v7

Motivation for or Use Case

Related issues or PR

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

[pascalgrimaud]

cc @deepu105 @jdubois
I'm adding a big bounty on this, as I think there is a lot of work to achieve this, but it would be really so cool to have it !

[atomfrede]

Let's see how fast then 3rd party components are getting compatible. They have postponed the migration utilities for now as far as I know (but not sure how much it would help in our case).

[pascalgrimaud]

@atomfrede : do you have more information ? I thought it would be compatible with Vue 3

[atomfrede]

Did not look in detail yet. I also guess we can upgrade without too much hassle. We have few 3rd party libraries and they are widely used. I try to have a look next week to get a better understanding what would be needed.

[pascalgrimaud]

I'd love to have this for JHipster v7
Don't hesitate to ask help, and if needed, we can add separate bounties for people who want to help here

[atomfrede]

At least bootstrap-vue is not yet compatible. They plan to have a compatible release "short" after vue 3 release. Will follow closely. https://github.com/bootstrap-vue/bootstrap-vue/issues/5196#issuecomment-668837891

[atomfrede]

For i18n there is already a beta version which we could try and use https://github.com/intlify/vue-i18n-next.

Both veeValidate and Vuelidate are not yet compatible out of box with vue3. But using the composition api it might be possible. I will try to finish the (finally) the eslint migration in the main generator and can try vue3 afterwards.

[chenhui7373]

vue3 compatible component: https://2x.antdv.com/docs/vue/introduce/
i18n support: https://2x.antdv.com/docs/vue/i18n/
dashboard: https://pro.antdv.com/docs/getting-started

[mrts]

@atomfrede note that a "migration build" is in the works with Vue 2 compatible behavior (and runtime warnings of incompatible usage). So perhaps an interim step would be to implement minimal changes to use the migration build even if this is not fully optimal and then follow up with a rewrite to composition API eventually.

Note that there is also Vite for Vue 3 which makes frontend development lightning fast.

[atomfrede]

As far as I understand the migration build is not yet available?

We are still working on a dedicated Migration Build of Vue 3 with Vue 2 compatible behavior and runtime warnings of incompatible usage. If you are planning to migrate a non-trivial Vue 2 app, we strongly recommend waiting for the Migration Build for a smoother experience.

[mrts]

As far as I understand the migration build is not yet available?

Yes, it is not yet available. According to the Vue 3 roadmap, it is planned to be released in Q4 2020.

[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]

simple comment to keep this opened:)

[gmarziou]

The keep-alive comment :)

[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

[atomfrede]

Keep it open.