Moqui 4.0 - Vue 3 Quasar 2 Upgrade

michael · May 13, 2025, 5:17pm

Current status of Vue 3 Quasar 2 is:

a new render mode qvt2 and screen path qapps2 have been added
there is NOT yet functionality for rendering qvue components like coarchy/template/EditProcessStory.qvue at 1f0d3b79a20b47581ef27e57a85c2b30293d75c9 · coarchy/coarchy · GitHub

The main thing that needs to be done is to test and fix existing apps and screens.

If each of you can run the vue3quasar2 branches on your current Moqui setup and either report OR fix submit a pr of the fixes that would be a great first step.
To run use the vue3quasar2 branch of:

moqui-framework
moqui-runtime
SimpleScreens
MarbleERP

If one of you would like to volunteer applying changes similar to Comparing master…vue3quasar2 · moqui/SimpleScreens · GitHub for HiveMind and PopCommerce that would be great.

Also if you’re adventurous, let me know and you could give the implementation of rendering qvue2 a shot.

shahbaz · May 14, 2025, 5:03am

Thank you for the update. I will proceed with testing the vue3quasar2 branches for the specified repositories and report or submit PRs for any issues found.

newmannhu · June 1, 2025, 12:56am

@michael
Upgrading vue2 to vue3 and quasar1 to quasar2 mainly solves the following problems:

Differences between Vue3 and Vue2 in creating root instances and registering components
The router management methods in Vue3 are different, Quasar requires the router to support the ‘to’ attribute
Upgrading http-vue-loader

I used a different approach than you when dealing with router upgrades. After testing, such changes have minimal impact on the original code and have passed basic tests on components such as tools, Marble ERP, PopCommerce, HiveMind, and example.

Please review the PR to see if it is feasible.

update qapps/vapps to vue3 and quasar2 by newmann · Pull Request #235 · moqui/moqui-runtime