You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is reproduction for me on a plain templated app created using yarn create vite vue-lang-test --template vue-ts
The App.vue file is parsing correctly, the components/HelloWorld.vue file is showing Cannot find module '@/helpers/GetMenuContext'. Did you mean to set the 'moduleResolution' option to 'nodenext', or to add aliases to the 'paths' option?ts-plugin(2792) on the import line.
No amount of restarting vs, ts language service, etc. seemed to help.
Rolling back to 1.8.27 solves this for me. All of the 2.0.* versions seem to have this problem.
I originally found this on an app with a somewhat more complex directory structure, which leads me to believe it's just .vue files (and thus related to the vue language service rather than just .ts) and that it's only files exactly one level below the src director (or two below the *.tsconfig file.
All of the imports in the .vue files in the components directory show the error.
None of the .ts files in the components directory show this error. None of the .ts or .vue files under the pages directory (which are at least one level more nested) show this error. While my app doesn't have this by default, adding another level of nesting under components doesn't show the error in the .vue files and adding a .vue file directly under pages does show the error.
This is reproduction for me on a plain templated app created using
yarn create vite vue-lang-test --template vue-ts
The
App.vue
file is parsing correctly, thecomponents/HelloWorld.vue
file is showingCannot find module '@/helpers/GetMenuContext'. Did you mean to set the 'moduleResolution' option to 'nodenext', or to add aliases to the 'paths' option?ts-plugin(2792)
on the import line.No amount of restarting vs, ts language service, etc. seemed to help.
Rolling back to
1.8.27
solves this for me. All of the2.0.*
versions seem to have this problem.I originally found this on an app with a somewhat more complex directory structure, which leads me to believe it's just .vue files (and thus related to the vue language service rather than just .ts) and that it's only files exactly one level below the
src
director (or two below the *.tsconfig file.All of the imports in the
.vue
files in thecomponents
directory show the error.None of the
.ts
files in thecomponents
directory show this error. None of the.ts
or.vue
files under thepages
directory (which are at least one level more nested) show this error. While my app doesn't have this by default, adding another level of nesting under components doesn't show the error in the.vue
files and adding a.vue
file directly underpages
does show the error.The text was updated successfully, but these errors were encountered: