Same here! This is causing me quite some pain right now.
I have a project with client and server (node) sources in the same project but with different roots and different tsconfig.json files:
tsconfig.json (for server sources in
tsconfig.json (for client sources in
This worked perfectly a little while ago, but not any more now.
EDIT: I found out this seems to happen just with that one project. In another project (though it contains only a single tsconfig) it works properly and atom-typescript is also properly rewriting the config file.
EDIT 2: After some more testing I found out that the reason it doesn't work doesn't seem related to having 2 tsconfig files or a new atom-typescript version. Instead (at least in my case) this seems to be related to #921, Atom shows me for all files "no tsconfig found".
Then I tried removing / adding some directories and files until I got it working again.
By doing that I found out that once I removed the
node_modules directory in my root folder, atom-typescript would properly recognize both tsconfig files again.
EDIT 3: Some more testing later:
It looks like this was caused because I had a
npm linked module in my node_modules which didn't exist in the global package store any more (i.e. the junktion (windows symlink) was invalid),