These are chat archives for TypeStrong/atom-typescript

12th
Sep 2016
Dominic Watson
@intellix
Sep 12 2016 07:47
is there any known issue with performance when dealing with angular-cli generated projects in particular? I'm not certain it's to do with particular projects, but there's more information here: https://github.com/TypeStrong/atom-typescript/issues/969#issuecomment-246270518
@Ptival this is exactly my issue. VSCode gives me instant autocomplete suggestions for imports and method usage etc, yet atom-typescript queues up requests and sometimes just stops working entirely. I don't understand what VSCode is doing so differently to make a world of a difference
atom-typescript for me so far has never been usable but I never read about any particular issue for it. Is it largely known about? What am I doing wrong :D
Dominic Watson
@intellix
Sep 12 2016 07:56
if I have errors in my code it pretty much just stops giving me autocomplete info. I don't think it's to do with TS 2.0.0 either, as I had the same issues with TS 1.8.x as well
Valentin Robert
@Ptival
Sep 12 2016 14:43
@intellix do you get to use vscode-tslint with tsc >= 2?
Dominic Watson
@intellix
Sep 12 2016 14:44
aye, you get a warning saying something like: "the CLI is 1.8.0 and this project uses 2.0.2, would you like to use 2.0.2?" - Yes/No
you click yes, and it's using 2.0.2, works perfectly :D
Valentin Robert
@Ptival
Sep 12 2016 14:44
wow really!?
Valentin Robert
@Ptival
Sep 12 2016 14:45
for me it just used 1.8 and started complaining about "readonly" and other 2.0 features
Dominic Watson
@intellix
Sep 12 2016 14:45
VS Code now checks if the workspace folder contains a custom TypeScript version (typically installed via npm install typescript@x.x.x). If this is the case and the typescript.tsdk setting isn't used, then VS Code informs the user about the local version and ask whether the local version should be used.
and it still works super fast, which is why it's confusing as to how VSCode can be so much faster
Valentin Robert
@Ptival
Sep 12 2016 14:46
@intellix oh, but do you use the vscode-tslint plugin, or how do you get your errors?
maybe the plugin is unneeded to get TS support?
oh wait
it's new in 1.5.1
Dominic Watson
@intellix
Sep 12 2016 14:47
didn't check tslint stuff, will try it now if there's a plugin
Valentin Robert
@Ptival
Sep 12 2016 14:47
I tried in 1.4.0
I will try again today
thanks!
Dominic Watson
@intellix
Sep 12 2016 14:47
The vscode-eslint and vscode-tslint extensions now provide settings to run the linter only on save and not while typing.
anyone else have anymore information about the performance of atom-typescript? there's a mile of a difference. Figured someone would have some information as to what's happening there
Valentin Robert
@Ptival
Sep 12 2016 18:50
@intellix Thanks! yeah it's so much faster :') too bad I like atom-typescript a lot but I'm going to be using vscode for a bit I think