[Nuxt/Vite] paths in types are absolute. Incompatible with WSL2 and WebStorm

[misaon]

Environment

Nitro 2.5.2
Node 18.17

Reproduction

nuxt/nuxt#21827 (comment)

Describe the bug

Why is the .nuxt folder and its dt.ts so inconsistent? Some places are relative imports, some places are absolute. WebStorm can't handle absolute paths in WSL2, so Nuxt 3 is unusable in that environment. It would make much more sense to me if all imports were relative.

Additional context

No response

Logs

No response

[misaon]

https://github.com/unjs/nitro/blob/8c0473ca28a3ce170d5cf2cbfd0634889fb6881b/src/build.ts#L164C15-L164C15

[danielroe]

I believe this is already resolved on the edge. Would you check?

[misaon]

Much better but still contains bugs, reopen. 😞
nuxt/nuxt#21827 (comment)

[misaon]

@danielroe Do you think it would be good to have support for controlling tsconfig.server.json in hook prepare:types? Similar to tsconfig.json for Nuxt. Currently it can only be controlled via the typescript propert in: defineNuxtConfig > nitro > typescript > tsConfig.

https://github.com/nuxt/nuxt/blob/20efac7d57fd66283140a224d653d92b6e41676a/packages/nuxt/src/core/nitro.ts#L355C13-L355C23

[misaon]

@danielroe @pi0 I just tested and unfortunately it still doesn't work properly... 😞

Nuxt 3.7.0-28201370.c8cba7a0 with Nitro 2.6.0-28201391.6af6fd1

.nuxt/tsconfig.server.json: OK
.nuxt/types/nitro-imports.d.ts: BAD

// ...
export { defineCachedFunction, defineCachedEventHandler, cachedFunction, cachedEventHandler, useRuntimeConfig, useStorage, useNitroApp, defineNitroPlugin, nitroPlugin, defineRenderHandler, getRouteRules, useAppConfig, useEvent } from '/home/xxx/Projects/upscore/node_modules/.pnpm/nitropack-edge@2.6.0-28201391.6af6fd1/node_modules/nitropack-edge/dist/runtime';
// ...

[danielroe]

@misaon Would you provide a reproduction?

[misaon]

@misaon Would you provide a reproduction?

nuxt/nuxt#21827 (comment)

[misaon]

@danielroe tested, works great.