Types broken inside api routes

[madebyfabian]

Environment

• Operating System: Darwin
• Node Version: v18.16.1
• Nuxt Version: 3.7.4
• CLI Version: 3.9.0
• Nitro Version: 2.6.3
• Package Manager: pnpm@8.6.7
• Builder: -
• User Config: devtools, experimental, typescript, vite, app, modules, image, graphql-client, site
• Runtime Modules: @nuxtjs/tailwindcss@6.8.0, nuxt-icons@3.2.1, @nuxt/image@1.0.0-rc.3, nuxt-graphql-client@0.2.30, @nuxtseo/module@2.0.0-beta.35
• Build Modules: -

Describe the bug

I want to use a graphql operation server-side.

1. This works, but is not typed:

   export default defineEventHandler(async event => {
   const data = await GqlSendContactFormRequest() 
   
   return {
       data, // -> any
   }
   })

2. I tried to import it like this. Now types work, But this breaks the runtime. Since I am importing types as a const.

import { GqlSendContactFormRequest } from '#gql'
// ...

3. The hacky way: Types & Runtime works, but I don't think it should be like this.

   
   import type { GqlSendContactFormRequest as RequestT } from '#gql'

export default defineEventHandler(async event => { const data = (await GqlSendContactFormRequest()) as typeof RequestT

return {
    data, // -> Correct type
}

})

---

Are these methods not intended to use server-side? I think some of the latest nuxt releases might broke this module, since server typed are handled seperately in a `server/tsconfig.json` now.

### Expected behaviour

I expect the operation methods to work without having to manually type them

### Reproduction

_No response_

### Additional context

_No response_

### Logs

_No response_

[iBobik]

Another possible workaround is to import return type:

import type { ListOrderPacketsInTransportQuery } from '#gql'

export default defineTask({
  async run({ payload, context }) {
    const { orderItems }: ListOrderPacketsInTransportQuery = await GqlListOrderPacketsInTransport()

I remember it worked in a past too. Considering many other server-side related issues it seems @Diizzayy does not use GraphQL server-side in his projects. ;-) Anything we can do for you to help you with server-side features and bugs?