Skip to content
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

Closed
akdor1154 opened this issue Oct 4, 2016 · 8 comments · Fixed by #748 · May be fixed by #720
Closed

Typescript-Sublime-Plugin should allow per-project specification of typescript_tsdk #538

akdor1154 opened this issue Oct 4, 2016 · 8 comments · Fixed by #748 · May be fixed by #720

Comments

@akdor1154
Copy link

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:

  • Allow specification of typescript_tsdk in Sublime's project settings.
  • Automatically check if 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.
@elsimir
Copy link

elsimir commented Oct 5, 2016

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.

@fiznool
Copy link

fiznool commented Jan 12, 2017

"typescript_tsdk": "./node_modules/typescript/lib" works for me in my user settings, to enable per-project specification. I'm on Ubuntu 16.10.

EDIT: actually, it doesn't. It seemed to work but I get the following in the ST console.

Exception in thread Thread-4:
Traceback (most recent call last):
  File "./python3.3/threading.py", line 901, in _bootstrap_inner
  File "./python3.3/threading.py", line 858, in run
  File "/home/fiznool/.config/sublime-text-3/Packages/TypeScript/typescript/libs/node_client.py", line 149, in monitorPostQueue
    self.server_proc.stdin.flush()
BrokenPipeError: [Errno 32] Broken pipe

@amir-arad
Copy link

any updates on this one? It's a real blocker for me

@jussikinnula
Copy link

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.

@olierxleben
Copy link

want to ping this topic! Really blocks usage with st3

@faergeek
Copy link

faergeek commented Sep 2, 2019

Is there any update on this? This is a must have feature for me.

alecmev added a commit to alecmev/TypeScript-Sublime-Plugin that referenced this issue May 26, 2020
Fix microsoft#538

This plugin is unusable without this change when dealing with Yarn PnP projects.
@orta orta closed this as completed in #748 Jun 8, 2020
@raineorshine
Copy link

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 typescript_tsdk which references a project-relative path (i.e. "node_modules/typescript/lib"), but does not support a project-specific typescript_tsdk in .sublime-project. Can you confirm?

I was wondering why .sublime-project is not supported, but maybe it's not so important since a project-relative path can be specified in the global setting. I tend to prefer project-specific settings.

@StabbarN
Copy link

I'm also having problem setting typescript_tsdk in .sublime-project. Setting typescript_tsdk only works as a global user setting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
10 participants