Closed andreww2012 closed 1 year ago
Describe the bug Type checking of <nuxt-link>'s to prop stops working if an import statement from #components is present in SFC, but only after running nuxt dev.
<nuxt-link>
to
#components
nuxt dev
Expected behavior Errors are not ignored.
Environnement infos
Nuxi 3.6.5 - Operating System: Windows_NT - Node Version: v16.16.0 - Nuxt Version: 3.6.5 - Nitro Version: 2.5.2 - Package Manager: pnpm@8.6.10 - Builder: vite - User Config: devtools, modules, imports - Runtime Modules: nuxt-typed-router@3.2.5 - Build Modules: -
Your pages folder structure Your nuxt.config.ts
pages
Reproduction with instructions: https://github.com/andreww2012/nuxt-typed-router-no-errors-when-adding-components-import
I see, the native definition of NuxtLink should be removed by Nuxt-typed-router. I'll look at it
Fixed in 3.3.1 @andreww2012 , keep me updated!
3.3.1
Thank you, it's working now! 🥇
Describe the bug Type checking of
<nuxt-link>
'sto
prop stops working if an import statement from#components
is present in SFC, but only after runningnuxt dev
.Expected behavior Errors are not ignored.
Environnement infos
Your
pages
folder structure Your nuxt.config.tsReproduction with instructions: https://github.com/andreww2012/nuxt-typed-router-no-errors-when-adding-components-import