Hello can you provide a reproduction please ?

you can use https://stackblitz.com/edit/nuxt-starter-uvbiaa?file=README.md .

I need at least the package.json with the lockfile n order to debug it

Yes, here's the reproduction: https://stackblitz.com/edit/nuxt-starter-geb6an?file=server%2Fplugins%2Fmongodb.ts

Steps:

1. Create .env file and add MONGODB_URI=mongodb+srv into it
2. See the "server/plugins/mongodb.ts" file - the env from useRuntimeConfig() is unknown

Then:
4. Remove 'nuxt-applicationinsights' from nuxt.config.ts modules
5. Go back to "server/plugins/mongodb.ts" file - the env from useRuntimeConfig() is now a string as it should be

I am having exactly the same issue, is there a fix coming? Thanks!

that's strange, I can't reproduce it from https://stackblitz.com/edit/nuxt-starter-geb6an?file=server%2Fplugins%2Fmongodb.ts

BTW V1 is coming soon. but i can do a release patch on 0.x if i can reproduce it.

It's still reproducible for me, when I open the link, I have the TS error, as soon as I remove the 'nuxt-applicationinsights' from nuxt.config.ts, the TS error goes away.

Tested the V1, still the same issue. Also I've found what's it caused by:

in src/runtime/types.d.ts on line 5 the declaration is incorrect, if you change it to:

declare module 'nuxt/schema' {

the types will start working.

So i finally understood why i couldn't reproduce it. I was using pnpm. The workaround for now is to use pnpm as we need to investigate this specific issue in nuxt first.

You can see the reason of augmenting @nuxt/schema instead of nuxt/schema here and here in nuxt

which version of node and npm are you using ?
So i do reproduce it on stackblitz with npm only, not pnpm. But i can't reproduce it locally with npm nor pnpm

I'm getting this issue on Node v20 and Node v22, did not test other versions. For packages Yarn 1.22 is used, but I don't think the issue is related to node or npm / yarn version.

Most likely the types are just incorrectly implemented, but I don't know the right way of doing it as I never developed a Nuxt module before. I just know that changing it back to nuxt/schema "fixes" the "TS unknown" issue.

Also when reproducing it, make sure that you are testing the types on server side (some server side plugin or some API endpoint) as I'm not sure if there's same issue on FE code.