[nuxt] instance is not available in server utils unit tests with useRuntimeConfig()

[alexcroox]

Environment

• Operating System: Darwin
• Node Version: v20.10.0
• Nuxt Version: 3.13.2
• CLI Version: 3.13.2
• Nitro Version: 2.9.7
• Package Manager: [email protected]
• Builder: -
• User Config: compatibilityDate, devtools, future, experimental, ssr, typescript, routeRules, hooks, runtimeConfig, extends, modules, sourcemap, ui, postcss, tailwindcss, vite, nitro, components, css, imports, content, ogImage, i18n
• Runtime Modules: @nuxt/test-utils/[email protected], @pinia/[email protected], @nuxt/[email protected], @nuxtjs/[email protected], @nuxt/[email protected], @vueuse/[email protected], @nuxt/[email protected], [email protected], @nuxt/[email protected], @nuxtjs/[email protected], @nuxt/[email protected], @codecov/[email protected], @nuxtjs/[email protected]
• Build Modules: -

Reproduction

https://stackblitz.com/edit/github-gu1sj1-si6cpn?file=server%2Futils%2Fexample-util.nuxt.spec.ts&startScript=start

Run -> npm run test

Describe the bug

After some recent dependancy upgrades around Nuxt I'm getting the [nuxt] instance unavailable error on tests that call functions in server/utils that use useRuntimeConfig.

See the reproduction link for an example. Thanks.

Additional context

No response

Logs

No response

[stackblitz]

Start a new pull request in StackBlitz Codeflow.

• github-gu1sj1-xnyzbk (Open reproduction)

[danielroe]

The runtime environment for nuxt test utils is for testing client-side/browser code, rather than server code. (See #531.) So I wouldn't expect it to work.

Does code using useRuntimeConfig work fine when outside the server/ folder?

[alexcroox]

ah that's a real shame. It used to work before compatibility version 4 was introduced, here is a repro with it working fine in the old folder structure: https://stackblitz.com/edit/github-gu1sj1-xnyzbk?file=server%2Futils%2Fexample-util.nuxt.spec.ts&startScript=start

and yes useRuntimeConfig works outside the server folder in v4