Interesting internals causing SSR not to initialise a utils class

[silverbackdan]

I have an issue where on server-side loads, the store does not expect quite as I'd expect and a class method seems to be able to be called without a constructor calling first. I've decided on a code structure to initialise complex stores for my Nuxt module.

I initialise my stores:
https://github.com/components-web-app/cwa-nuxt-module/blob/feat/components/src/runtime/storage/storage.ts

And each creates the store definition e.g.:
https://github.com/components-web-app/cwa-nuxt-module/blob/feat/components/src/runtime/storage/stores/resources/resources-store.ts

Then in my getters I have some common functionality I want to split out for ease of testing:
https://github.com/components-web-app/cwa-nuxt-module/blob/feat/components/src/runtime/storage/stores/resources/getters.ts#L28

You'll see that this should initialise here:
https://github.com/components-web-app/cwa-nuxt-module/blob/feat/components/src/runtime/storage/stores/resources/getter-utils.ts

However, on server-side, this function is called from a getter the resourcesState property is undefined
https://github.com/components-web-app/cwa-nuxt-module/blob/feat/components/src/runtime/storage/stores/resources/getter-utils.ts#L10

It is only that function, so I imagine that I am not calling the other on server-side.

Does anyone have an idea why this would be the case?

I'm on the latest version of Nuxt.

[silverbackdan]

OK so I see the issue.
If I define a getter in a computed variable to return a function, I guess somewhere, perhaps vue internals, this causes the error.

So instead of

resourcesApiStateIsPending: computed(() => {
      return utils.resourcesApiStateIsPending
    })

Using

resourcesApiStateIsPending: computed(() => {
      return (resources: string[]) => (utils.resourcesApiStateIsPending(resources))
    })

will work