Auto Import Types Not Resolving in latest v1.11.0

Open
#373 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
nuxtjs, typescript
Domain
developer-experience, frontend

Research direction

Reproduce the issue with @nuxt/icon 1.11.0, Nuxt 3.16.0, Vue 3.5.13, and the provided Nuxt configuration. Start by tracing the auto-imported Icon type generation or resolution and compare it with v1.10.3. Done means VS Code reports missing props and displays the component's available props again.

Written by the indexing model from the issue text.

Description

The latest version v1.11.0 does not properly resolve the auto imported type of Icon

With the previous v1.10.3 - the auto imported Icon component shows a type error if missing props and also shows available props in the VS Code context window:

Image

With v1.11.0 - the Icon component does not show any type errors if missing props and the available props are not displayed by VS Code:

Image

Using dependencies:

{
    "@nuxt/icon": "1.11.0",
    "nuxt": "^3.16.0",
    "vue": "^3.5.13",
    "vue-router": "^4.5.0"
}

With latest nuxt config:

export default defineNuxtConfig({
  compatibilityDate: '2024-11-01',
  devtools: { enabled: true },
  modules: ['@nuxt/icon']
})
Dominant language
TypeScript
Stars
1.2k
Forks
96
Avg merge
8h 12m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nuxt/icon

All issues in nuxt/icon

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.