after update from 4.2.1 to 4.2.2 not work autocomplete in webstorm

[FlexIDK]

Environment

Node.js version v24.12.0
nuxt/cli version 3.31.2
Package manager npm 11.7.0
Nuxt version 4.2.2
Nitro version 2.12.9
Builder vite 7.2.7

Reproduction

update from 4.2.1 to 4.2.2 and rebuild .nuxt folder or create new vue component

Describe the bug

After running npm run dev, the file .nuxt/types/components.d.ts contains an incorrect path to components.

• In version 4.2.1, the path is generated as:
  'ComponentName': typeof import("../../app/components/component-name.vue")['default']

• In version 4.2.2, the path is generated as:
  'ComponentName': typeof import("../../app/components/component-name.vue").default

After this change, autocomplete and "Go to Declaration" in WebStorm (JetBrains) stop working.
If manually replace .default with ['default'], autocomplete works again.

Additional context

No response

Logs

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

🔗 Similar Issues

Related Issues

• The import path of the auto-generated component types is incorrect #33121
• Incorrect relative imports in .nuxt/types/components.d.ts cause broken IDE navigation and missing autocomplete #33143
• [v4] Lint error – Warnings on auto-imports in extended folders #32633

🔗 Related PRs

#29869 - fix(nuxt): assign default name to component without setup [merged]
#30043 - fix: remove unused dependencies and tidy project [merged]
#30148 - fix(nuxt): nuxt and nuxt/app resolutions [merged]
#33122 - fix(nuxt): correct relative path of auto imported components [merged]
#33373 - fix(nuxt): support autoimports' typeFrom property when generating type templates [merged]

👤 Suggested Assignees

• akfakf0509
• DharmarajX24
• luigigorlero
• huang-julien
• danielroe

---

🧪 Issue enrichment is currently in early access.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

[github-actions]

Would you be able to provide a minimal reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritize it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

Please use a template below to create a minimal reproduction

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

• The Importance of Reproductions
• How to Generate a Minimal, Complete, and Verifiable Example

[FlexIDK]

v4.2.2
look file: .nuxt/types/components.d.ts
interface _GlobalComponents { 'Test': typeof import("../../app/components/test.vue").default

v4.2.1
look file: .nuxt/types/components.d.ts
interface _GlobalComponents { 'Test': typeof import("../../app/components/test.vue")['default']

[Flo0806]

In my eyes .default is a standard and reserved keyword in javascript. Also it is fine. the knitwork 1.3.0 did the change.

1. We can ask knitwork if they give us a special option to become [default] instead of .default.
2. Webstorm should fix this "issue", because it is correct javascript
3. We modify Nuxt to make this

2 should be the way I guess.

[cernymatej]

Agreed. This is something JetBrains should probably fix.

[yhagus]

Is this fixed yet in any WebStorm version?

[n0-m4d]

i stumbled upon the same issue and spent hours figuring out that downgrading from 4.2.2 to 4.2.1 fixes it. the latest phpstorm version still cant handle it.

[cernymatej]

Is there an open issue in YouTrack? If not, would you please open one? 🙏

[n0-m4d]

Is there an open issue in YouTrack? If not, would you please open one? 🙏

https://youtrack.jetbrains.com/issue/WEB-76306/