should help you out Got it, I was using Visual Studio 2019 Preview and for some reason 2017 worked fine. Turns out I just needed to install the 3.2.2 SDK and everything worked perfectly in both versions. I don't know why 2017 didn't care that the SDK wasn't installed and 2019 did, seems odd.
should help you out When you add a tsconfig.json file, the whole directory becomes a single project. Typescript will compile it as a project instead of compiling each file individually. You’ll have to remove that file. Either switch to another editor or contact the authors of atom-typescript and let them know about this.
Hope that helps typescript-eslint does not report compiler warnings. It only reports warnings generated by its own validation rules. Also, enabling the strict option in TypeScript has no effect on the code analysis performed by typescript-eslint, which does not rely on the project settings. There have been some discussions about creating a new @typescript-eslint/no-undef rule (modeled on ESLint no-undef rule) that would catch at least some of the warnings generated by the tsc compiler with strict type checking on.