Switch Vue microfrontends to use recently released @module-federation/[email protected]

[mshima]

Overview of the feature request

Vue is still using webpack as microfrontend.
With vite alternative reaching v1.0.0 it’s time to try the switch again.

Version 1.0.0 switched to @module-federation/runtime from @softarc/native-federation which is not responsive angular-architects/module-federation-plugin#367, angular-architects/module-federation-plugin#324

Motivation for or Use Case

Related issues or PR

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

[gioboa]

I'm a core team member of module federation vite, I would like to help with this activity

[DanielFran]

@gioboa All help is welcome. See #27493

[mshima]

Following #27493 @module-federation/vite is not a viable alternative for us:

• does not support custom cache folder we use target for maven and build for gradle.
• does not support custom shared config and prints wrong info to console
• breaks vite tests

[gioboa]

I see, is there any possibility for improving on our side?

[mshima]

@gioboa the sample that uses vue with module-federation is ms-mf-vue-consul-oauth2-mysql-memcached.
You can download it directly through app-ms-mf-vue-consul-oauth2-mysql-memcached link or in CI artifacts https://github.com/jhipster/generator-jhipster/actions/runs/11220830980?pr=27493.

It's possible to run in workspaces root scripts like npm run ci:e2e:package and npm run ci:frontend:test or vite in each workspace.
There are too many upstream adjusts needed for me to try to fix. If they are fixed we can resume this issue.