Navigation Menu

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

Request completionItem/resolve failed. #1983

Closed
lincycode opened this issue Oct 11, 2022 · 8 comments
Closed

Request completionItem/resolve failed. #1983

lincycode opened this issue Oct 11, 2022 · 8 comments
Labels
bug Something isn't working

Comments

@lincycode
Copy link

Today suddenly appeared, what is this

Kapture.2022-10-11.at.15.52.32.mp4
@lincycode
Copy link
Author

Message: Request completionItem/resolve failed unexpectedly without providing any details.

@johnsoncodehk
Copy link
Member

Could you try can this problem reproduce in https://github.com/johnsoncodehk/volar-starter?

@lincycode
Copy link
Author

Could you try can this problem reproduce in https://github.com/johnsoncodehk/volar-starter?

I tried but it didn't reproduce the problem.
This is what happens when I import "some" components (don't know what the difference)

This information comes from volar, maybe it's related to this? (did not exist before)
image

@Mondotosz
Copy link

Mondotosz commented Oct 14, 2022

I'm having the same issue since a few days and the intellisense stopped working for imports.
I downgraded the @types/node package since that was on the known issues but it doesn't fix it.

Here I had suggestions for imports alongside their packages
image
Now I have to manually specify the source before I can get any suggestion which is pretty annoying
image

edit: rolling back to v.0.40.13 fixes the intellisense issues, waiting for a fix.

@vhud
Copy link

vhud commented Oct 16, 2022

Same issue since the update on 10/14. The component gets imported properly but this error is annoying. Custom components color scheme changed as well, which I don't see mentioned anywhere on the changelog. The color change be unrelated as I hadn't restarted vscode in a while.
vueFailed

@johnsoncodehk
Copy link
Member

@Mondotosz This is different problem, you can open a new issue for it.

@vhud, @1059845833 I can't reproduce this problem, could you provide repro case?

@lincycode
Copy link
Author

@Mondotosz This is different problem, you can open a new issue for it.

@vhud, @1059845833 I can't reproduce this problem, could you provide repro case?
My latest project is in my repository (vue3-music), I have tested other projects (including vite and vue-cli) without reproducing the problem.
I re-clone this project and found no problem importing modules, the only difference with other projects is that the bottom tag will have a "1 known issue"(no response after clicking) message from volar , but my original project still have this problem.

@vhud
Copy link

vhud commented Oct 16, 2022

@johnsoncodehk
Have you tried creating a small vue cli project with the prior version of the plugin, then upgrading the plugin and attempting to create a new component? I'll try to nail down solid reproduction steps when I have more time, but this is something to try in the meantime.

@johnsoncodehk johnsoncodehk added the bug Something isn't working label Oct 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants