tsconfig.json
tsconfig.json
, which will usually make everything Just Work™. In general, you may customize your TypeScript build process as usual using the tsconfig.json
file."outDir"
and sets "noEmit"
to true
. The default configuration we generate allows you to run editors which use the compiler without creating extraneous .js
files throughout your codebase, leaving the compilation to ember-cli-typescript to manage.tsconfig.json
if 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 "noEmit"
to 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.outDir
won'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.target
key in tsconfig.json
to the current version of the ECMAScript standard so that type-checking uses the latest and greatest from the JavaScript standard library. The Babel configuration in your app's config/targets.js
and any included polyfills will determine the final build output.tsconfig.json
(using the "include"
, "exclude"
, or "files"
keys), you will need to restart the server to take the changes into account: ember-cli-typescript does not currently watch the tsconfig.json
file. For more details, see the TypeScript reference materials for tsconfig.json
.ember-cli-build.js
file:tsconfig.json
. (Current versions generate the correct config at installation.) Either run ember generate ember-cli-typescript
or verify you have the same sourcemap settings in your tscsonfig.json
that appear in the blueprint.