VSCode cannot resolve Nuxt Auto Imports in a new/renamed file

[kingychiu]

In my current vscode setup, Nuxt and vue typescript is working fine. But when I rename or create a file, the type and resolution wont work on that new file only. Any ideas?

Project/Folder Setup, it is under a workspace:

/app-backend
/app-frontend
/app-frontend/tsconfig.json # This refs /app-frontend/.nuxt/tsconfig.json

I found that in the existing file, tsconfig is found:

But in a new file, no tsconfig is found:

For example, let's say I have a composable named useABC
VSCode can auto-suggest this when I type useAB only on an existing file.

AutoImport is working on an existing file:

After renaming, the resolution becomes different:

After restarting the entire VSCode, it will work again. Since now the vue restart command is removed (#4164), only restarting VSCode can resolve the issue.

[davidmatter]

You can execute the "Reload Window" command. No need to restart VSCode. I have the same problem in a conventional Vue3 project, without nuxt, in 2.0.7.

[johnsoncodehk]

This problem should be fixed in the master branch, here are the relevant commits:

• volarjs/volar.js@6d7a542
• volarjs/volar.js@17d1fa2
• volarjs/volar.js@baf5a99

We need to wait for VSCode 1.88 to be released before we can update the extension. You can use 1.8.27 for now.

[johnsoncodehk]

The restart command was re-add by #4174.