SSR. Prefetch guard in router.beforeResolve on client don't call

[209]

What happened?

Prefetch doesn't call in client

What did you expect to happen?

// quasar client-entry.js

    router.isReady().then(() => {
      // but router.beforeResolve call before addPreFetchHooks
      addPreFetchHooks({ router, store, publicPath })
      app.mount('#q-app')
    })

addPreFetchHooks in client-prefetch.js adding next :

   router.beforeResolve((to, from, next) => {
     // don't call
     ....
   })

And quasar guard don't call...

Reproduction URL

https://stackblitz.com/edit/quasarframework-stackblitz-templates-dukolyes?file=src%2FApp.vue

How to reproduce?

1. Go to link
2. quasar dev -m ssr
3. see console

Flavour

Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)

Areas

Quasar CLI Commands/Configuration (@quasar/cli | @quasar/app-webpack | @quasar/app-vite)

Platforms/Browsers

No response

Quasar info output

Relevant log output

Additional context

No response

[yusufkandemir]

Hi there 👋 It's really unclear what you want/expect. It first calls preFetch, then mounts the component, which is the expected behavior.
Please use your native language and use AI/translators to translate to English, instead of directly writing in English. It's hard to understand this way.

[209]

@yusufkandemir

Sorry for my English.

I expect prefetch in App.vue to work in SSR exactly the same way as in noSSR — that is, to be called on the client as well. Then the store itself can decide whether it should actually perform a prefetch or not.

Inside prefetch, I run some fine-grained app initialization logic before Vue is mounted.
Why: I’m experimenting with enabling/disabling SSR, and I don’t want to move this asynchronous logic into boot files.

For example, right now I don’t understand why prefetch on router pages is called every time the user navigates to that page. It’s no longer needed — the first run already happened.
I understand why this happens technically, but I don’t understand why it’s designed this way.

Either I don’t understand the philosophy behind this feature, or I’m using it incorrectly.