nuxt server environment support

[danielroe]

We currently support running composables/components in a browser-type environment (with happy-dom, and soon jsdom). But there are use cases where it might be useful to support running tests in a hybrid server environment where things like h3 utilities and nuxt ssr utilities work.

This could definitely be classed as non-essential and experimental, but we can track it here.

[silverbackdan]

Thanks for opening this issue. There are probably cases, such as using <ClientOnly>, but in my use case it would be simply mocking process.client and process.server for a couple of unit tests.

It seems that I can't do this in simple unit tests even for those tests which are not running this Nuxt environment once the plugin is installed.

[danielroe]

Nuxt hard codes process.client and process.server to true/false based on environment, to enable tree-shaking. (So there is no process object that can be manipulated.)

[silverbackdan]

I see, thanks for the clarification

[rubennaatje]

as a work around for my apicalls / nitro plugins i added all auto imported server stuff to my setup.ts as

vitest.stubGlobal("defineEventHandler", (func: any) => func);
vitest.stubGlobal("defineNitroPlugin", (e: any) => e);
//etc

Which works absolutely fine for the time being, if anyone has a better idea/way i'd love to know!

I mock my own utilities the same way and then use them in unit tests like this

(getService as MockedFunction<typeof getService>).mockReturnValue(
  {mockedServiceCall: () => true}
);