How to remove the __INITIAL_STATE__ variable

[yahao87]

I'm using Quasar v1.
It works only as a PWA in the user's browser. Basically, we have a lot of data to store in common, so we're caching this data with localstorage.
And using SSR, it only responds to search engine bots.
Therefore, I do not need the INITIAL_STATE variable, and for optimization, the store must be managed as a singleton in the SSR server.
But I can't see any way to remove the INITIAL_STATE variable.
Too heavy data is being included in every SSR response.
Is there any way to remove the INITIAL_STATE variable?

[MilosPaunovic]

#5903

https://quasar.dev/quasar-cli-webpack/developing-ssr/configuring-ssr#manually-triggering-store-hydration

ssr: {
  manualStoreHydration: true/false,
    // Manually hydrate the store.
    // This is detailed in a subsection below
}

[yahao87]

What you've found is how to do the hydration manually.
What I'm looking for is a way to not export the store at all.

[yahao87]

I need a way to resolve responses that are over 1 megabyte(gziped) to every ssr page.
Help me.... T.T

[yusufkandemir]

If you are sure that you don't need state hydration in any way, you can do the following in store(s)/index.js or in a boot file.

// /src/store(s)/index.js
// ...

export default store(function ({ ssrContext }) {
  // ...

  if (process.env.SERVER && ssrContext) {
    ssrContext.onRendered(() => {
      // Disable
      ssrContext.state = undefined
    })
  }
  
  // ...
})

See ssrContext docs for explanation about state and onRendered

[yahao87]

thanks.
I tried to find it in v1 somehow with the clue you gave me.
But in v1 I can't find the rendered function.
Is there a similar feature in v1?

[yahao87]

@yusufkandemir
Now the SSR response is close to 5MB.
I can't update vue major version.
Should we give up the quasar SSR?
Help me make a decision.

[MilosPaunovic]

If you want to update Vue major version to 3.x.x, you have to switch to [email protected] - Quasar 1 utilizes [email protected].

[yahao87]

If you want to update Vue major version to 3.x.x, you have to switch to [email protected] - Quasar 1 utilizes [email protected].

I'm just saying I should use Quasar v1. I don't want to upgrade vue version.
Because the project size is large, it takes a lot of time to change it.
I just need to check.
Is there any solution.

[rstoenescu]

Going to implement this for Quasar v2 then backport to v1 also.
Please follow the progress in #13113

[rstoenescu]

@yahao87
The functionality that you want will be available through "@quasar/app" v2.3. In your quasar.conf.js file, add this:

// quasar.conf.js
ssr: {
  manualStoreSsrContextInjection: true
}

This won't add add the store state to the ssrContext and so it won't serialize and inject it into the server-side output.

I've scheduled multiple Quasar packages releases for tomorrow (April 8th) and this is included.

[yahao87]

wow.
I was thinking of another alternative.
I never thought you could add features so quickly.
Thank you so much.
I love quasar
Thanks again

[rstoenescu]

And I've just released the new stuff.
Donations from your company are appreciated to get the wheels going ;) https://donate.quasar.dev