-
Notifications
You must be signed in to change notification settings - Fork 32.6k
Problem with typescript.tsdk in vscode workspace #106563
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
Comments
The automatic change in settings is also happening with yarn v1 too. I'm sure it didn't happened in old versions as my workspace was using the same setup. |
Also, the |
Duplicate of #105202. Should already be fixed in the current insiders builds |
@mjbvz unfortunately this problem doesn't seem to be solved. I'm using yarn 2.3.1 (which strongly relies on workspace ts settings) in following environment: Version: 1.49.3 (system setup) Initial value of mine typescript.tsdk is: "typescript.tsdk": ".yarn/sdks/typescript/lib" and after "select ts to workspace version" it changes to absolute path. It's very not desired behavior, especially because workspace file is under version control. Worth to mention that, if you update the ts version to workspace one by "typescript.enablePromptUseWorkspaceTsdk": true popup then the path doesn't get updated. |
Uh oh!
There was an error while loading. Please reload this page.
I'm trying to configure yarn v2 pnpfy vscode + typescript sdk in a vscode workspace and yarn workspace with multiple projects.
I put
typescript.tsdk
setting in a relative path of the workspace (".yarn/sdks/typescript/lib"
or"./.yarn/sdks/typescript/lib"
).When opening vscode workspace and setting the typescript prompt, vscode updates the workspace setting and put the absolute path there. Of course this is not desired.
The text was updated successfully, but these errors were encountered: