Skip to content

[Bug]: compiler installed under VSCode folder will be used before the global one when LSP is starting without workspace opened #5581

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

Closed
4 tasks done
RodgeFu opened this issue Jan 13, 2025 · 1 comment
Assignees
Labels
bug Something isn't working ide Issues for VS, VSCode, Monaco, etc.

Comments

@RodgeFu
Copy link
Contributor

RodgeFu commented Jan 13, 2025

Describe the bug

If user installs compiler under vscode's folder (...\Programs\Microsoft VS Code\node_modules@typespec\compiler...) and our extension is activated without any workspace, the compiler under vscode folder will be used before the one installed compiler.

Reproduction

  1. install compiler under vscode folder and global
  2. activate our extension by command or opened tsp file
  3. check the compiler used by lsp

Checklist

@mzhongl524
Copy link
Member

can not repro

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ide Issues for VS, VSCode, Monaco, etc.
Projects
None yet
Development

No branches or pull requests

2 participants