-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
vue-language-server does not working when using workspaces #12019
Comments
I have a similar issue with this error in console:
In my case I am not using a workspace but Zed is opened on a monorepo with 2 distinct vue apps in subfolders (eg. If I open only one of the 2 apps directly in Zed everything works correctly |
1 whenever opening a project with the frontend inside of the project folder that's opened (e.g. in a headless application with |
@joshuaia I was able to reproduce the issue in v0.0.3 of the Vue extension. Once I upgraded to v0.1.0 of the extension (which was released earlier today), things seem to be working as expected. Could you give it a try with v0.1.0 and see if that fixes your issue? Also, thank you so much for including a clear repro and an example project. It made it very easy for me to test! |
@maxdeviant thanks a lot! |
Check for existing issues
Describe the bug / provide steps to reproduce it
After moving vue support from Zed to extension, in workspace dependent repositories
vue-language-server
stopped working.To reproduce:
pnpm i
(you may see some errors after the installation ends, you can skip them, they does not effect on this reproduction)pages
inhoppscotch-sh-admin
package)vue-language-server
It happens only for
vue-language-server
, ts server works well, you can try to open any ts file in this repo and you will see it in action.Environment
Zed: v0.135.2 (Zed)
OS: macOS 14.5.0
Memory: 16 GiB
Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your
~/Library/Logs/Zed/Zed.log
file to this issue.No response
The text was updated successfully, but these errors were encountered: