Skip to content
New issue

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

The import .vue file in the .ts file will not be able to locate #2950

Closed
4 tasks done
masquevil opened this issue May 21, 2021 · 3 comments
Closed
4 tasks done

The import .vue file in the .ts file will not be able to locate #2950

masquevil opened this issue May 21, 2021 · 3 comments

Comments

@masquevil
Copy link

  • I have searched through existing issues
  • I have read through docs
  • I have read FAQ
  • I have tried restarting VS Code or running Vetur: Restart VLS

Info

  • Platform: macOS
  • Vetur version: 0.33.1
  • VS Code version: 1.56.0

Problem

Bug 1

In the vscode editor, if you import a .vue file in a .ts or .js file, you will not be able to locate the file, only shims-vue.d.ts.
But there is no problem importing the .vue file in the .vue file:

Note that there is no entry.vue file in the dropbox:
dropbox

command + click to jump, it will jump to shims-vue.d.ts:
shims-vue.d.ts

Bug 2

The import .vue file in the .vue file can be located, but two modules will be found, which are the same file but in different scopes:

Found 2 modules:
Found 2 modules

Click the first one to enter, all the contents in the <script> tag will be selected:
selected area 1

Click the second one to enter, it will select from the <script> tag to the end of the file:
selected area 2

Bug 3

import Comp from './xxx/yyy'

If you do not write .vue or index.vue, the corresponding file cannot be recognized.

Reproducible Case

https://github.com/masquevil/stock

@satrong
Copy link

satrong commented May 25, 2021

the same to me.

@yoyo930021
Copy link
Member

Duplicate of #2591

@yoyo930021 yoyo930021 marked this as a duplicate of #2591 Jun 2, 2021
@masquevil
Copy link
Author

Bug 1 can follow: #2016
Bug 2 & 3 still not resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants