cannot resolve module path correctly with `resolvePath` on un-hoisted structure pacakges?nuxt/nuxt · updated1 year ago · 36% similar bugkit🔨 p3-minor✨ good reproduction
`tsconfig`: Folders outside of project are added if module name does not match filesystem pathnuxt/nuxt · closed6 months ago · 40% similar pending triage
It opens the .nuxt folder into node_modules/nuxt and gives wrong paths everywhere. - 3.15.3nuxt/nuxt · closed1 year ago · 36% similar pending triagecli
Wrong module resolution in tsconfig.json filenuxt/nuxt · closed1 year ago · 36% similar good first issuetypesbugkit🔨 p3-minor
Occur error when module path is a package subpath that does not match the actual pathnuxt/nuxt · closed1 year ago · 35% similar bug🔨 p3-minor
wrong file path is generated in `components.d.ts` for filename with multiple dotsnuxt/nuxt · closed1 year ago · 35% similar pending triage
Nuxt 4 - defineNuxtModule using nuxt.dir.public resolve to absolute pathnuxt/nuxt · closed2 years ago · 35% similar 3.xpending triageneeds reproduction
import from "~/..." or ".../..." do not resolve correctly in /server/modules/...tsnuxt/nuxt · closed9 months ago · 35% similar pending triageneeds reproduction
tsconfig paths not resolved with documented setup instructionsnuxt/test-utils · closed16 days ago · 35% similar pending triage