[Bug] Quasar 2: BeforeEach navigation guard is not firing for initial request while registered in boot files

Describe the bug BeforeEach navigation guard is not firing while it registered within boot file for direct navigation to our SPA.

Codepen/jsFiddle/Codesandbox (required) …

To Reproduce Put following code in .quasar/client-entry.js and see the console output for ‘First’ and ‘Second’ messages of guards.

createQuasarApp(createApp)
  .then(app =>
  {
    // Ok!
    app.router.beforeEach((to, from, next) =>
    {
      console.log(`First: navigated to ${to.fullPath}`);
      next();
    });

    return Promise.all([
      import(/* webpackMode: "eager" */ 'boot/i18n'),
      // import(/* webpackMode: "eager" */ 'boot/our-boot-file')
    ]).then(bootFiles =>
    {
      // Nope! This guard will not be called at startup.
      app.router.beforeEach((to, from, next) =>
      {
        console.log(`Second: navigated to ${to.fullPath}`);
        next();
      });

      const boot = bootFiles
        .map(entry => entry.default)
        .filter(entry => typeof entry === 'function')

      start(app, boot)
    })
  })

To ensure that second guard is working:

• navigate to any wrong url within SPA.
• click on “Go Home” button.
• console will show the ‘First’ and the ‘Second’ messages.

Expected behavior BeforeEach navigation guard must catch initial navigation request in boot files.

Platform (please complete the following information): OS: Windows 10 (1809) Node: v12.16.1 Yarn: 1.22.4 Browsers: Chrome 88.0.4324.146

[rstoenescu]

Fix will be available in “@quasar/app” v3.0.0-beta.2

[rstoenescu]

Would be a good idea to put that beforeEach hook code directly in /src/router/index.js