-
-
Notifications
You must be signed in to change notification settings - Fork 198
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
"Go To Definition" in VS Code does not work for Typescript projects using Yarn 2 PnP #940
Comments
Have you tried following this doc for yarn 2 pnp ? |
Yeah I was the one that noticed they didn't work any more with a recent change. Forgot to add that step into this issue description. |
You can try setting logging the message between language-server and the extension:
|
Hey there, I am experiencing a similar issue on vscode v1.61.2, with a clean SvelteKit project. For me, it only affects go to definition for HTML elements. See below for the error I get and relevant verbose log output. This may be related to yarnpkg/berry#3539. Happy to provide any further details that could help :). Logs
|
Describe the bug
When you're using Yarn 2 PnP with a typescript project, an error occurs when using "Go To Definition" on an imported symbol.
To Reproduce
npx degit sveltejs/template svelte-typescript-app
node scripts/setupTypeScript.js
yarn set version berry
ZipFS
extension is installed in VS CodeApp.svelte
fileError:
Note that this works when control-clicking a file in a
.ts
file in the same project. That makes me think that there's something going on in the transition between VS Code andtsserver
, which would besvelte-language-server
I think. I've looked around but haven't seen any discussion on this yet, but lots of discussions which enabled this support in the Typescript language server - something about passing file paths around that aren't literal paths on the system.Expected behavior
Same behavior as in a
.ts
file.System (please complete the following information):
svelete-language-server
The text was updated successfully, but these errors were encountered: