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
Typescript-Sublime-Plugin should allow per-project specification of typescript_tsdk #538
Comments
Additionally, allow setting the "typescript_tsdk" using relative paths as the .sublime-project can be shared across machines so "typescript_tsdk": "./node_modules/typescript/lib" is likely to be the most widely used path. |
EDIT: actually, it doesn't. It seemed to work but I get the following in the ST console.
|
any updates on this one? It's a real blocker for me |
I'm also interested on getting multiple TypeScript versions to be used in projects. I have some legacy projects which work with the bundled 2.2.x version, but for newer projects which use TypeScript 2.4.x especially async/await and string Enums give headache. I manually updated latest TypeScript to TypeScript-Sublime-Plugin to overcome the issue, but it would be nice if there would be a configuration option to at least override the bundled version with something newer globally. |
want to ping this topic! Really blocks usage with st3 |
Is there any update on this? This is a must have feature for me. |
Fix microsoft#538 This plugin is unusable without this change when dealing with Yarn PnP projects.
I see the task is closed but I'm not quite clear on the outcome. From my testing, it seems that it supports a global user setting for I was wondering why |
I'm also having problem setting |
Different projects can use different typescript versions, and it can be irritating to have to change Sublime's global config to change
typescript_tsdk
. Two things could alleviate this:typescript_tsdk
in Sublime's project settings.node_modules/typescript/lib
exists in a project, and if so, use it.The second option would quiet almost all of the 'how do I use a different version of typescript?' questions ever asked, as the project's build version would then be used by default in almost all cases.
The text was updated successfully, but these errors were encountered: