The problem with Quasar's SSR is that you'll be locked into their CLI tool due to how much undocumented global state changes they do.
If you just want use it as a UI component library in an existing Vue SSR app, you'd have to at the very least:
- Call Quasar.ssrUpdate before instantiating the root Vue app. The devs also stated they have no intention of releasing the type definition for this _essential_ function [1]
- Extract app.$q.ssrContext.Q_BODY_CLASSES and add it to your <body> tag during your render step or else most of the css states will not work
These are the two main culprits I've found. Sadly my SSR apps still feel slightly off compared to a SPA with missing animations here and there.
If you just want use it as a UI component library in an existing Vue SSR app, you'd have to at the very least:
- Call Quasar.ssrUpdate before instantiating the root Vue app. The devs also stated they have no intention of releasing the type definition for this _essential_ function [1]
- Extract app.$q.ssrContext.Q_BODY_CLASSES and add it to your <body> tag during your render step or else most of the css states will not work
These are the two main culprits I've found. Sadly my SSR apps still feel slightly off compared to a SPA with missing animations here and there.
[1] https://github.com/quasarframework/quasar/issues/8112#issuec...