Migrate frontend tooling : move from vue-cli to vite

[sbernard31]

This issue is part of #1492.

Why migrate from vue-cli to vite ?

Vue CLI is in Maintenance Mode!
For new projects, please use create-vue to scaffold Vite-based projects.
(source : https://cli.vuejs.org/)

Also, dependabot seems to report some vulnerability in library used by vue-cli.

Migration

I mainly using :

• https://vueschool.io/articles/vuejs-tutorials/how-to-migrate-from-vue-cli-to-vite/
• https://stackoverflow.com/a/71404291/5088764

I did some test in smaller project before :

• https://github.com/sbernard31/vuecli-to-vite-template
• https://github.com/sbernard31/vue2-vite-template
• https://github.com/sbernard31/vuetify2-vite-template

shared node in monorepo

Our 2 front-end project sharing code from leshan-servers-core-demo.
This shared code is not ever a real json module.
To solve this we need to define custom resolver in vite.config.js and we need to use @rollup/plugin-node-resolve" to explicitily define where is node_modules folder.

[sbernard31]

Build time benefits of the vue-cli => vite migration:

For mvn -f pom.xml clean install javadoc:javadoc -PeclipseJenkins -B command executed on Eclipse Jenkins :

Build Time of	Before (vue-cli)	After (vite 5)
leshan-server-demo	01:26 min	39.045 s
leshan-bsserver-demo	01:01 min	33.796 s
Full build	08:50 min	07:18 min

For mvn clean install -DskipTests command executed on my local dev machine :

Build Time of	Before (vue-cli)	After (vite 5)
leshan-server-demo	01:05 min	28.925 s
leshan-bsserver-demo	01:01 min	24.882 s
Full build	03:49 min	02:36 min

(It could improve : https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/3429)

[sbernard31]

Still some too big chunk with vite : #1239 (comment)

[sbernard31]

Get some little improvement with lighthouse score : #1240 (comment)

[sbernard31]

This now integrated in master : #1541