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

Regression: Custom extensions mostly stopped working in 2.0.6. #4072

Closed
cabal95 opened this issue Mar 11, 2024 · 2 comments
Closed

Regression: Custom extensions mostly stopped working in 2.0.6. #4072

cabal95 opened this issue Mar 11, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@cabal95
Copy link
Contributor

cabal95 commented Mar 11, 2024

This is related to #3977.

After updating the extension to 2.0.6 the custom extension files mostly do not work. Specifically, we don't get the red squiggles like we did in 2.0.0, but all the intellisense is gone. Hoving over anything does not pop anything up and trying other operations like "Go to definition" do not work. Tested in both the <template> section and the <script> section.

I don't have a screenshot because there is nothing to show. Meaning, it isn't that it pops up an empty tooltip or anything, just nothing happens. Nothing seems obvious in the commits - but maybe it is one of the dependencies from the volar.js repo.

I checked the TypeScript output and it seems normal enough:

2024-03-11 15:09:23.030 [info] Starting TS Server
2024-03-11 15:09:23.030 [info] Using tsserver from: c:\Users\Daniel\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js
2024-03-11 15:09:23.030 [info] <syntax> Forking...
2024-03-11 15:09:23.030 [info] <syntax> Starting...
2024-03-11 15:09:23.030 [info] <semantic> Forking...
2024-03-11 15:09:23.030 [info] <semantic> Starting...

The "Vue Language Server" output is completely blank. But it's also blank when I downgrade to 2.0.5, so maybe blank is normal.

@johnsoncodehk
Copy link
Member

Should be fixed in master branch. Please let me know if the problem still exists, thanks.

@cabal95
Copy link
Contributor Author

cabal95 commented Mar 31, 2024

Thank you @johnsoncodehk. As far as I can tell this is indeed fixed when running from the master branch today.

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

2 participants