My project's build outputs TypeScript-compiled Javascript in a separate build dir (`src\lib\foo.ts -> build\lib\foo.js`) to avoid polluting the source tree with build artefacts. It would be useful if it was possible to either: 1) Disable emit-on-save. 2) Be able to configure the options that the code is built with, including output directory and flags such as module type and noImplicitAny. Discussion on Gitter: > But valid suggestion to have atom-typescript config. Please open an issue : > https://github.com/TypeStrong/atom-typescript/issues and this will be the first config option we add I see a reference to tsconfig.json which will apparently be a standard way to configure TypeScript in future but I don't know too much about the plans for it. Would that be another way to address this use case? # Admin task list - [ ] add emit on save plugin option + architecture for watched configurations. - [x] add `tsconfig` TypeScript PR to docs. https://github.com/Microsoft/TypeScript/pull/1692