How to properly disable auto imports

[lunar widget]

Since this my fifth time (or so) experiencing issues with nuxt auto-importing the wrong thing (without me or TS noticing) I wanted to disable auto imports all together. Since I struggle to do so correctly, I want to ask three questions:

What did I try?

I added the following to my nuxt config, but things are still broken:

  imports: {
    autoImport: false,
  },

1. Duplicated imports XXX
I still get errors like Duplicated imports "createError", the one from "#app" has been ignored, although I thought I disabled auto import. Why?

2. Typescript
Disabling auto-imports does not seem to work properly in connection with TS. I have cases where my typescript errors, although I need the line to run. i.e.:

import { fromNodeMiddleware } from '#imports';

errors with Module '"#imports"' has no exported member 'fromNodeMiddleware'., but if I remove the line and try to run I get the following runtime error: [worker reload] [worker init] defineNitroPlugin is not defined

I have other cases where I typescript fails to give errors. i.e. I have to import useRuntimeConfig from #imports manually to prevent getting a useRuntimeConfig is not defined runtime error (which is expected) , but TS fails to detect the issue during build time.

3. Where to import Nuxt / Nitro utilities from?
There are some nuxt / nitro utils that I have no idea where to import from if not from #imports. i.e. useRuntimeConfig, definePageMeta, defineNitroPlugin or fromNodeMiddleware. From where do I import those?

Thanks a lot in advance 🙃

[nimble sphinx]

I know very well your pain and if I could, I would completely remove auto-import and magic paths like #apps, #imports and so on! Would be much clear and safe just import it from the correct library and live in peace.
Did you find any solution? I am struggling so much with IDE + TypeScript checks and all these magic. =/

[lunar widget]

No sadly I could not find any real solution to this. I guess Auto-Imports is just something we have to live with 😅

[atomic forum]

I have a large application that disables auto-importing. But I don’t suffer from the issues you’ve outlined. IDE issues are often an isolated issue, something that’s very hard to reproduce without stepping into your shoes.

In regards to magic paths, there’s no real magic here. These are virtual modules that make it easier for end-users, as much as internal usage, to idiomatically communicate between varying environments (I.e. server/client). Life would be much more complicated without them.

[lunar widget]

for me it's not only IDE issues, but actually tsc complaining...

would you mind sharing your config?

[atomic forum]

Do you have a tsconfig in your server directory? I know there isn’t full coverage for type checking support in the server env, as acknowledged in the docs…

[lunar widget]

I jsut have the default setup, which is automatically generated when initializing a new project 🙈

so no tsconfig for the server directory