Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Use globally installed typescript by default
See original GitHub issueRight now the plugin checks for typescript_tsdk value in the sublime settings, and, if it isn’t present, it uses tsserver.js from the plugin directory.
I believe it should check if there is a tsserver available on PATH and use that (if typescript_tsdk isn’t set obviously). I can’t think of a scenario where a developer has typescript globally installed and wants to use one that is shipped with an editor plugin.
Also It would be cool to check if there is a locally installed typescript in a project folder and use it for that specific project.
If you guys are cool with this proposal, I will be happy to work on a PR for this.
Cheers!
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Wouldn’t it make more sense to first look for a local version of TypeScript, (installed per project via
npm i -D typescript) to avoid problems with legacy projects using older versions of TS, then check for a global and only then fallback to whatever we currently have?It is sufficient when you know about it. Personally I learned that is exists while trying to figure out why does the plugin give me errors when the command line compiler works fine. So the expected behavior was that it should use the installed typescript, am I wrong?