TypeScript 2.6 introduces a new strict checking flag, --strictFunctionTypes.\nThe --strictFunctionTypes switch is part of the --strict family of switches, meaning that it defaults to on in --strict mode.\nYou can opt-out by setting --strictFunctionTypes false on your command line or in your tsconfig.json.
Under --strictFunctionTypes function type parameter positions are checked contravariantly instead of bivariantly.\nFor some background on what variance means for function types check out What are covariance and contravariance?.
The stricter checking applies to all function types, except those originating in method or constructor declarations.\nMethods are excluded specifically to ensure generic classes and interfaces (such as Array<T>) continue to mostly relate covariantly.
Consider the following example in which Animal is the supertype of Dog and Cat:
\ntsdeclare let f1: (x: Animal) => void;\ndeclare let f2: (x: Dog) => void;\ndeclare let f3: (x: Cat) => void;\nf1 = f2; // Error with --strictFunctionTypes\nf2 = f1; // Ok\nf2 = f3; // Error
The first assignment is permitted in default type checking mode, but flagged as an error in strict function types mode.\nIntuitively, the default mode permits the assignment because it is possibly sound, whereas strict function types mode makes it an error because it isn’t provably sound.\nIn either mode the third assignment is an error because it is never sound.
\nAnother way to describe the example is that the type (x: T) => void is bivariant (i.e. covariant or contravariant) for T in default type checking mode, but contravariant for T in strict function types mode.
\ntsinterface Comparer<T> {\n compare: (a: T, b: T) => number;\n}\n\ndeclare let animalComparer: Comparer<Animal>;\ndeclare let dogComparer: Comparer<Dog>;\n\nanimalComparer = dogComparer; // Error\ndogComparer = animalComparer; // Ok
The first assignment is now an error. Effectively, T is contravariant in Comparer<T> because it is used only in function type parameter positions.
By the way, note that whereas some languages (e.g. C# and Scala) require variance annotations (out/in or +/-), variance emerges naturally from the actual use of a type parameter within a generic type due to TypeScript’s structural type system.
Under --strictFunctionTypes the first assignment is still permitted if compare was declared as a method.\nEffectively, T is bivariant in Comparer<T> because it is used only in method parameter positions.
\ntsinterface Comparer<T> {\n compare(a: T, b: T): number;\n}\n\ndeclare let animalComparer: Comparer<Animal>;\ndeclare let dogComparer: Comparer<Dog>;\n\nanimalComparer = dogComparer; // Ok because of bivariance\ndogComparer = animalComparer; // Ok
TypeScript 2.6 also improves type inference involving contravariant positions:
\n\ntsfunction combine<T>(...funcs: ((x: T) => void)[]): (x: T) => void {\n return x => {\n for (const f of funcs) f(x);\n }\n}\n\nfunction animalFunc(x: Animal) {}\nfunction dogFunc(x: Dog) {}\n\nlet combined = combine(animalFunc, dogFunc); // (x: Dog) => void
Above, all inferences for T originate in contravariant positions, and we therefore infer the best common subtype for T.\nThis contrasts with inferences from covariant positions, where we infer the best common supertype.
TypeScript 2.6 fixes the tagged string template emit to align better with the ECMAScript spec.\nAs per the ECMAScript spec, every time a template tag is evaluated, the same template strings object (the same TemplateStringsArray) should be passed as the first argument.\nBefore TypeScript 2.6, the generated output was a completely new template object each time.\nThough the string contents are the same, this emit affects libraries that use the identity of the string for cache invalidation purposes, e.g. lit-html.
\ntsexport function id(x: TemplateStringsArray) {\n return x;\n}\n\nexport function templateObjectFactory() {\n return id`hello world`;\n}\n\nlet result = templateObjectFactory() === templateObjectFactory(); // true in TS 2.6
Results in the following generated code:
\n\njs\"use strict\";\nvar __makeTemplateObject = (this && this.__makeTemplateObject) || function (cooked, raw) {\n if (Object.defineProperty) { Object.defineProperty(cooked, \"raw\", { value: raw }); } else { cooked.raw = raw; }\n return cooked;\n};\n\nfunction id(x) {\n return x;\n}\n\nvar _a;\nfunction templateObjectFactory() {\n return id(_a || (_a = __makeTemplateObject([\"hello world\"], [\"hello world\"])));\n}\n\nvar result = templateObjectFactory() === templateObjectFactory();
\n\nNote: This change brings a new emit helper,
\n__makeTemplateObject;\nif you are using--importHelperswithtslib, an updated to version 1.8 or later.
TypeScript 2.6 npm package ships with localized versions of diagnostic messages for 13 languages.\nThe localized messages are available when using --locale flag on the command line.
Error messages in Russian:
\n\nshc:\\ts>tsc --v\nVersion 2.6.0-dev.20171003\n\nc:\\ts>tsc --locale ru --pretty c:\\test\\a.ts\n\n../test/a.ts(1,5): error TS2322: Тип \"\"string\"\" не может быть назначен для типа \"number\".\n\n1 var x: number = \"string\";\n ~
And help in Japanese:
\n\nshPS C:\\ts> tsc --v\nVersion 2.6.0-dev.20171003\n\nPS C:\\ts> tsc --locale ja-jp\nバージョン 2.6.0-dev.20171003\n構文: tsc [オプション] [ファイル ...]\n\n例: tsc hello.ts\n tsc --outFile file.js file.ts\n tsc @args.txt\n\nオプション:\n -h, --help このメッセージを表示します。\n --all コンパイラ オプションをすべて表示します。\n -v, --version コンパイラのバージョンを表示します。\n --init TypeScript プロジェクトを初期化して、tsconfig.json ファイルを作成します。\n -p ファイルまたはディレクトリ, --project ファイルまたはディレクトリ 構成ファイルか、'tsconfig.json' を含むフォルダーにパスが指定されたプロジェクトをコ\nンパイルします。\n --pretty 色とコンテキストを使用してエラーとメッセージにスタイルを適用します (試験的)。\n -w, --watch 入力ファイルを監視します。\n -t バージョン, --target バージョン ECMAScript のターゲット バージョンを指定します: 'ES3' (既定)、'ES5'、'ES2015'、'ES2016'、'ES2017'、'ES\nNEXT'。\n -m 種類, --module 種類 モジュール コード生成を指定します: 'none'、'commonjs'、'amd'、'system'、'umd'、'es2015'、'ESNext'。\n --lib コンパイルに含めるライブラリ ファイルを指定します:\n 'es5' 'es6' 'es2015' 'es7' 'es2016' 'es2017' 'esnext' 'dom' 'dom.iterable' 'webworker' 'scripthost' 'es201\n5.core' 'es2015.collection' 'es2015.generator' 'es2015.iterable' 'es2015.promise' 'es2015.proxy' 'es2015.reflect' 'es2015.symbol' 'es2015.symbol.wellkno\nwn' 'es2016.array.include' 'es2017.object' 'es2017.sharedmemory' 'es2017.string' 'es2017.intl' 'esnext.asynciterable'\n --allowJs javascript ファイルのコンパイルを許可します。\n --jsx 種類 JSX コード生成を指定します: 'preserve'、'react-native'、'react'。\n -d, --declaration 対応する '.d.ts' ファイルを生成します。\n --sourceMap 対応する '.map' ファイルを生成します。\n --outFile ファイル 出力を連結して 1 つのファイルを生成します。\n --outDir ディレクトリ ディレクトリへ出力構造をリダイレクトします。\n --removeComments コメントを出力しないでください。\n --noEmit 出力しないでください。\n --strict strict 型チェックのオプションをすべて有効にします。\n --noImplicitAny 暗黙的な 'any' 型を含む式と宣言に関するエラーを発生させます。\n --strictNullChecks 厳格な null チェックを有効にします。\n --noImplicitThis 暗黙的な 'any' 型を持つ 'this' 式でエラーが発生します。\n --alwaysStrict 厳格モードで解析してソース ファイルごとに \"use strict\" を生成します。\n --noUnusedLocals 使用されていないローカルに関するエラーを報告します。\n --noUnusedParameters 使用されていないパラメーターに関するエラーを報告します。\n --noImplicitReturns 関数の一部のコード パスが値を返さない場合にエラーを報告します。\n --noFallthroughCasesInSwitch switch ステートメントに case のフォールスルーがある場合にエラーを報告します。\n --types コンパイルに含む型宣言ファイル。\n @<ファイル>
TypeScript 2.6 support suppressing errors in .js files using // @ts-ignore comments placed above the offending lines.
\ntsif (false) {\n // @ts-ignore: Unreachable code error\n console.log(\"hello\");\n}
A // @ts-ignore comment suppresses all errors that originate on the following line.\nIt is recommended practice to have the remainder of the comment following @ts-ignore explain which error is being suppressed.
Please note that this comment only suppresses the error reporting, and we recommend you use this comments very sparingly.
\ntsc --watchTypeScript 2.6 brings a faster --watch implementation.\nThe new version optimizes code generation and checking for code bases using ES modules.\nChanges detected in a module file will result in only regenerating the changed module, and files that depend on it, instead of the whole project.\nProjects with large number of files should reap the most benefit from this change.
The new implementation also brings performance enhancements to watching in tsserver.\nThe watcher logic has been completely rewritten to respond faster to change events.
\nTypeScript 2.6 adds revised implementation the --noUnusedLocals and --noUnusedParameters compiler options.\nDeclarations are only written to but never read from are now flagged as unused.
Bellow both n and m will be marked as unused, because their values are never read. Previously TypeScript would only check whether their values were referenced.
\ntsfunction f(n: number) {\n n = 0;\n}\n\nclass C {\n private m: number;\n constructor() {\n this.m = 0;\n }\n}
Also functions that are only called within their own bodies are considered unused.
\n","headings":[{"value":"Strict function types","depth":2},{"value":"Example","depth":5},{"value":"Note","depth":5},{"value":"Cache tagged template objects in modules","depth":2},{"value":"Example","depth":5},{"value":"Localized diagnostics on the command line","depth":2},{"value":"Example","depth":5},{"value":"Suppress errors in .ts files using ’// @ts-ignore’ comments","depth":2},{"value":"Example","depth":5},{"value":"Faster tsc --watch","depth":2},{"value":"Write-only references now flagged as unused","depth":2},{"value":"Example","depth":5},{"value":"Example","depth":5}],"frontmatter":{"permalink":"/docs/handbook/release-notes/typescript-2-6.html","title":"TypeScript 2.6"}}},"pageContext":{"slug":"/docs/handbook/release-notes/typescript-2-6.html","isOldHandbook":true}}}tsfunction f() {\n f(); // Error: 'f' is declared but its value is never read\n}