Running a boot file prior to router initialization in Quasar CLI

[JoseGoncalves]

Hi,

I've hit a similar issue that the one reported at #14914, were I need to initialize a Vue Plugin before initializing the Vue Router in Quasar CLI. It seems that the current Quasar boot structure does not allow this, as the boot files are only executed after the router is initiated. My workaround for this was as following:

router/index.js

import { defineRouter } from '#q-app/wrappers';
import { createRouter, createWebHistory } from 'vue-router';
import routes from './routes';

export default defineRouter(() => {
	return () => {};
});

export const initRouter = () => {
	const history = createWebHistory(import.meta.env.BASE_URL);
	return createRouter({ history, routes });
};

boot/vue-plugin.js

import { defineBoot } from '#q-app/wrappers';
import { vueAsyncPlugin } from '<path_to_vue_async_plugin>';
import { initRouter } from '../router';

export default defineBoot(async ({ app }) => {
	await vueAsyncPlugin.install(app);

	app.use(initRouter());
});

Is this how it's supposed to handle this scenario in Quasar CLI, or is there a better (proper) way?
A drawback of my workaround is that other boot files for my app will not be able to access the Router instance.

[JoseGoncalves]

After looking at the Quasar's source code for the booting process, one cleaner way to support this use case would be to pass the Vue app instance when calling createRouter at http://github.com/quasarframework/quasar/blob/dev/app-vite/templates/entry/app.js#L111 and then one could handle the Vue plugin initialization in router/index.js.
What Quasar devs think of this idea?