These are chat archives for TypeStrong/atom-typescript

28th
Apr 2015
Navid Nikpour
@nvdnkpr
Apr 28 2015 13:46
Hey everyone
is there a possibility to disable the automatic generation of the tsconfig.json
Vaughn Royko
@vaughnroyko
Apr 28 2015 17:23
@basarat Having issues the last week with the new versions, it seems related to what @Mitranim is experiencing. Atom TypeScript no longer knows what "DataView" is for example. Even setting "declare var DataView: any;" is not working. Other examples include texImage2D (WebGL) giving "Supplied parameters do not match any signature of call target." even though it worked previously and uses the proper format. I can't find any information online about these two issues.
Matt Traynham
@mtraynham
Apr 28 2015 20:04
@vaughnroyko have an example of the code to share?
Basarat Ali Syed
@basarat
Apr 28 2015 22:01

Other examples include texImage2D (WebGL) giving "Supplied parameters do not match any signature of call target." even though it worked previously and uses the proper format. I can't find any information online about these two issues.

I think it might be related to TypeScript lib.d.ts update. Try reverting this package.json change : https://github.com/TypeStrong/atom-typescript/commit/85c424af1bdb68c7a16c3aa0ec7f9a6700441979#diff-b9cfc7f2cdf78a7f4b91a753d10865a2L37 and run npm install again and then open your repo.

is there a possibility to disable the automatic generation of the tsconfig.json

@nvdnkpr we only work of file system files. Tsconfig.json is vital to have a correct compilation context / any meaningful analysis of your code (e.g. which compiler target / to compiler on save or not to compile on save etc. )