Responses not typed in VS Code

[BorisKamp]

Environment

• Operating System: Darwin
• Node Version: v20.10.0
• Nuxt Version: 3.15.1
• CLI Version: 3.19.1
• Nitro Version: 2.10.4
• Package Manager: [email protected]
• Builder: -
• User Config: runtimeConfig, graphql-client, site, seo, devtools, nitro, build, css, modules, components, googleFonts, pwa, i18n, image, gtm, sentry, compatibilityDate
• Runtime Modules: @nuxtjs/[email protected], @kevinmarrec/[email protected], @nuxtjs/[email protected], @nuxt/[email protected], @nuxtjs/[email protected], @pinia/[email protected], [email protected], @nuxtjs/[email protected], @sentry/nuxt/[email protected], @nuxtjs/[email protected], @zadigetvoltaire/[email protected]
• Build Modules: -

Describe the bug

I remember in the past, that responses from Gql... auto created functions were typed, but in my recent project, that is no more.
See my screenshot here:

response is any here...

In .nuxt/gql/default.ts I see the OrdersQuery generated, but it is not used somehow?

Does anybody have a clue? It is very annoying that I get those TS errors because responses are any

Expected behaviour

The responses to be typed

Reproduction

No response

Additional context

No response

Logs

No response

[dacaga]

Same here, for SSR code only. Vuejs files seem to be using types from .nuxt/types/imports.d.ts and are typed properly. I can manually change the typeof import in nitro-imports.d.ts from typeof import('#gql-nitro') to typeof import('#gql') and it then works for server side code.

[dacaga]

Probably related to #333 and its proposed fix!

[BorisKamp]

Probably related to #333 and its proposed fix!

That sounds good, when can we expect the fix in a release? And does that also mean the broken fragments are fixed?