true. The default configuration we generate allows you to run editors which use the compiler without creating extraneous
.jsfiles throughout your codebase, leaving the compilation to ember-cli-typescript to manage.
tsconfig.jsonif your use case requires it, however. For example, to see the output of the compilation in a separate folder you are welcome to set
"outDir"to some path and set
false. Then tools which use the TypeScript compiler (e.g. the watcher tooling in JetBrains IDEs) will generate files at that location, while the Ember.js/Broccoli pipeline will continue to use its own temp folder.
outDirwon't have any effect on how Ember builds your application—we run the entire build pipeline through Babel's TypeScript support instead of through the TypeScript compiler.
config/targets.jsand any included polyfills will determine the final build output.
"files"keys), you will need to restart the server to take the changes into account: ember-cli-typescript does not currently watch the
tsconfig.jsonfile. For more details, see the TypeScript reference materials for
tsconfig.json. (Current versions generate the correct config at installation.) Either run
ember generate ember-cli-typescriptor verify you have the same sourcemap settings in your
tscsonfig.jsonthat appear in the blueprint.