We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug
When using VSCode Vue Official extension, nuxt auto imported components are typed as unknown with nuxt-typed-router.
vuejs/language-tools#4170
Expected behavior Auto imported components shall be well typed.
Screenshots
I use nuxt 3 and Vue Official 2.X+
Built-in and auto imported components are typed as unknown :
Even though they are in the .nuxt/components.d.ts
Imported by the .nuxt/tsconfig.json
.nuxt/tsconfig.json extended by my project tsconfig.json
Environnement infos
------------------------------ - Operating System: Linux - Node Version: v20.11.0 - Nuxt Version: 3.11.1 - CLI Version: 3.11.1 - Nitro Version: 2.9.4 - Package Manager: npm@10.5.0 - Builder: - - User Config: app, modules, experimental, tailwindcss, security, css, ssr, eslint, imports, runtimeConfig, plugins, build, vite, devServer, devtools, $test - Runtime Modules: nuxt-security@1.2.2, @nuxtjs/eslint-module@4.1.0, @vueuse/nuxt@10.9.0, @nuxtjs/tailwindcss@6.11.4, @nuxt/test-utils/module@3.12.0, nuxt-typed-router@3.6.1, @pinia/nuxt@0.5.1, () - Build Modules: - ------------------------------
Your pages folder structure
pages
pages ├── account │ └── index.vue ├── index.vue ├── login.vue
Your nuxt.config.ts
nuxt.config.ts modules config :
modules: [ 'nuxt-security', '@nuxtjs/eslint-module', '@vueuse/nuxt', '@nuxtjs/tailwindcss', '@nuxt/test-utils/module', 'nuxt-typed-router', ['@pinia/nuxt', { autoImports: ['defineStore'] }], (_, nuxt) => { nuxt.hooks.hook('vite:extendConfig', (config) => { config.plugins?.push(vuetify()); }); }, ], tailwindcss: { viewer: false }, security: { headers: { crossOriginEmbedderPolicy: 'unsafe-none', contentSecurityPolicy: { 'img-src': ['*', 'blob: data:'], 'script-src-attr': false, }, }, },
The text was updated successfully, but these errors were encountered:
The problem comes from the TypedNuxtLink GlobalComponents definition. it breaks the GlobalComponents typing.
When I remove the declore module 'vue', it works just fine.
Sorry, something went wrong.
I successfully reproduced adding vuetify and nuxt typed router to a clear nuxt install : https://github.com/ThomasBerneHCSE/issue-4170-repro
I used npm as the default package manager.
Sorry to respond only now @ThomasBerne , it looks like a regression because of a Nuxt change, i'll look
No branches or pull requests
Describe the bug
When using VSCode Vue Official extension, nuxt auto imported components are typed as unknown with nuxt-typed-router.
vuejs/language-tools#4170
Expected behavior
Auto imported components shall be well typed.
Screenshots
I use nuxt 3 and Vue Official 2.X+
Built-in and auto imported components are typed as unknown :
Even though they are in the .nuxt/components.d.ts
Imported by the .nuxt/tsconfig.json
.nuxt/tsconfig.json extended by my project tsconfig.json
Environnement infos
Your
pages
folder structureYour nuxt.config.ts
nuxt.config.ts modules config :
The text was updated successfully, but these errors were encountered: