Improvements in Inference and Promise.all

Recent versions of TypeScript (around 3.7) have had updates to the declarations of functions like Promise.all and Promise.race. Unfortunately, that introduced a few regressions, especially when mixing in values with null or undefined.

  1. ts
    interface Lion {
  2.   roar(): void;
  3. }
  5. interface Seal {
  6.   singKissFromARose(): void;
  7. }
  9. async function visitZoo(
  10.   lionExhibit: Promise<Lion>,
  11.   sealExhibit: Promise<Seal | undefined>
  12. ) {
  13.   let [lion, seal] = await Promise.all([lionExhibit, sealExhibit]);
  14.   lion.roar(); // uh oh
  15.   //  ~~~~
  16.   // Object is possibly 'undefined'.
  17. }

This is strange behavior! The fact that sealExhibit contained an undefined somehow poisoned type of lion to include undefined.

Thanks to a pull request from Jack Bates, this has been fixed with improvements in our inference process in TypeScript 3.9. The above no longer errors. If you’ve been stuck on older versions of TypeScript due to issues around Promises, we encourage you to give 3.9 a shot!

What About the awaited Type?

If you’ve been following our issue tracker and design meeting notes, you might be aware of some work around a new type operator called awaited. This goal of this type operator is to accurately model the way that Promise unwrapping works in JavaScript.

We initially anticipated shipping awaited in TypeScript 3.9, but as we’ve run early TypeScript builds with existing codebases, we’ve realized that the feature needs more design work before we can roll it out to everyone smoothly. As a result, we’ve decided to pull the feature out of our main branch until we feel more confident. We’ll be experimenting more with the feature, but we won’t be shipping it as part of this release.

Speed Improvements

TypeScript 3.9 ships with many new speed improvements. Our team has been focusing on performance after observing extremely poor editing/compilation speed with packages like material-ui and styled-components. We’ve dived deep here, with a series of different pull requests that optimize certain pathological cases involving large unions, intersections, conditional types, and mapped types.

Each of these pull requests gains about a 5-10% reduction in compile times on certain codebases. In total, we believe we’ve achieved around a 40% reduction in material-ui’s compile time!

We also have some changes to file renaming functionality in editor scenarios. We heard from the Visual Studio Code team that when renaming a file, just figuring out which import statements needed to be updated could take between 5 to 10 seconds. TypeScript 3.9 addresses this issue by changing the internals of how the compiler and language service caches file lookups.

While there’s still room for improvement, we hope this work translates to a snappier experience for everyone!

// @ts-expect-error Comments

Imagine that we’re writing a library in TypeScript and we’re exporting some function called doStuff as part of our public API. The function’s types declare that it takes two strings so that other TypeScript users can get type-checking errors, but it also does a runtime check (maybe only in development builds) to give JavaScript users a helpful error.

  1. ts
    function doStuff(abc: string, xyz: string) {
  2.   assert(typeof abc === "string");
  3.   assert(typeof xyz === "string");
  5.   // do some stuff
  6. }

So TypeScript users will get a helpful red squiggle and an error message when they misuse this function, and JavaScript users will get an assertion error. We’d like to test this behavior, so we’ll write a unit test.

  1. ts
    expect(() => {
  2.   doStuff(123, 456);
  3. }).toThrow();

Unfortunately if our tests are written in TypeScript, TypeScript will give us an error!

  1. ts
    doStuff(123, 456);
  2. //          ~~~
  3. // error: Type 'number' is not assignable to type 'string'.

That’s why TypeScript 3.9 brings a new feature: // @ts-expect-error comments. When a line is prefixed with a // @ts-expect-error comment, TypeScript will suppress that error from being reported; but if there’s no error, TypeScript will report that // @ts-expect-error wasn’t necessary.

As a quick example, the following code is okay

  1. ts
    // @ts-expect-error
  2. console.log(47 * "octopus");

while the following code

  1. ts
    // @ts-expect-error
  2. console.log(1 + 1);

results in the error

  1. Unused '@ts-expect-error' directive.

We’d like to extend a big thanks to Josh Goldberg, the contributor who implemented this feature. For more information, you can take a look at the ts-expect-error pull request.

ts-ignore or ts-expect-error?

In some ways // @ts-expect-error can act as a suppression comment, similar to // @ts-ignore. The difference is that // @ts-ignore will do nothing if the following line is error-free.

You might be tempted to switch existing // @ts-ignore comments over to // @ts-expect-error, and you might be wondering which is appropriate for future code. While it’s entirely up to you and your team, we have some ideas of which to pick in certain situations.

Pick ts-expect-error if:

  • you’re writing test code where you actually want the type system to error on an operation
  • you expect a fix to be coming in fairly quickly and you just need a quick workaround
  • you’re in a reasonably-sized project with a proactive team that wants to remove suppression comments as soon affected code is valid again

Pick ts-ignore if:

  • you have an a larger project and and new errors have appeared in code with no clear owner
  • you are in the middle of an upgrade between two different versions of TypeScript, and a line of code errors in one version but not another.
  • you honestly don’t have the time to decide which of these options is better.

Uncalled Function Checks in Conditional Expressions

In TypeScript 3.7 we introduced uncalled function checks to report an error when you’ve forgotten to call a function.

  1. ts
    function hasImportantPermissions(): boolean {
  2.   // ...
  3. }
  5. // Oops!
  6. if (hasImportantPermissions) {
  7.   //  ~~~~~~~~~~~~~~~~~~~~~~~
  8.   // This condition will always return true since the function is always defined.
  9.   // Did you mean to call it instead?
  10.   deleteAllTheImportantFiles();
  11. }

However, this error only applied to conditions in if statements. Thanks to a pull request from Alexander Tarasyuk, this feature is also now supported in ternary conditionals (i.e. the cond ? trueExpr : falseExpr syntax).

  1. ts
    declare function listFilesOfDirectory(dirPath: string): string[];
  2. declare function isDirectory(): boolean;
  4. function getAllFiles(startFileName: string) {
  5.   const result: string[] = [];
  6.   traverse(startFileName);
  7.   return result;
  9.   function traverse(currentPath: string) {
  10.     return isDirectory
  11.       ? //     ~~~~~~~~~~~
  12.         // This condition will always return true
  13.         // since the function is always defined.
  14.         // Did you mean to call it instead?
  15.         listFilesOfDirectory(currentPath).forEach(traverse)
  16.       : result.push(currentPath);
  17.   }
  18. }

https://github.com/microsoft/TypeScript/issues/36048

Editor Improvements

The TypeScript compiler not only powers the TypeScript editing experience in most major editors, it also powers the JavaScript experience in the Visual Studio family of editors and more. Using new TypeScript/JavaScript functionality in your editor will differ depending on your editor, but

CommonJS Auto-Imports in JavaScript

One great new improvement is in auto-imports in JavaScript files using CommonJS modules.

In older versions, TypeScript always assumed that regardless of your file, you wanted an ECMAScript-style import like

  1. js
    import * as fs from "fs";

However, not everyone is targeting ECMAScript-style modules when writing JavaScript files. Plenty of users still use CommonJS-style require(...) imports like so

  1. js
    const fs = require("fs");

TypeScript now automatically detects the types of imports you’re using to keep your file’s style clean and consistent.

For more details on the change, see the corresponding pull request.

Code Actions Preserve Newlines

TypeScript’s refactorings and quick fixes often didn’t do a great job of preserving newlines. As a really basic example, take the following code.

  1. ts
    const maxValue = 100;
  3. /*start*/
  4. for (let i = 0; i <= maxValue; i++) {
  5.   // First get the squared value.
  6.   let square = i ** 2;
  8.   // Now print the squared value.
  9.   console.log(square);
  10. }
  11. /*end*/

If we highlighted the range from /*start*/ to /*end*/ in our editor to extract to a new function, we’d end up with code like the following.

  1. ts
    const maxValue = 100;
  3. printSquares();
  5. function printSquares() {
  6.   for (let i = 0; i <= maxValue; i++) {
  7.     // First get the squared value.
  8.     let square = i ** 2;
  9.     // Now print the squared value.
  10.     console.log(square);
  11.   }
  12. }

Extracting the for loop to a function in older versions of TypeScript. A newline is not preserved.

That’s not ideal - we had a blank line between each statement in our for loop, but the refactoring got rid of it! TypeScript 3.9 does a little more work to preserve what we write.

  1. ts
    const maxValue = 100;
  3. printSquares();
  5. function printSquares() {
  6.   for (let i = 0; i <= maxValue; i++) {
  7.     // First get the squared value.
  8.     let square = i ** 2;
  10.     // Now print the squared value.
  11.     console.log(square);
  12.   }
  13. }

Extracting the for loop to a function in TypeScript 3.9. A newline is preserved.

You can see more about the implementation in this pull request

Quick Fixes for Missing Return Expressions

There are occasions where we might forget to return the value of the last statement in a function, especially when adding curly braces to arrow functions.

  1. ts
    // before
  2. let f1 = () => 42;
  4. // oops - not the same!
  5. let f2 = () => {
  6.   42;
  7. };

Thanks to a pull request from community member Wenlu Wang, TypeScript can provide a quick-fix to add missing return statements, remove curly braces, or add parentheses to arrow function bodies that look suspiciously like object literals.

TypeScript fixing an error where no expression is returned by adding a `return` statement or removing curly braces.

Support for “Solution Style” tsconfig.json Files

Editors need to figure out which configuration file a file belongs to so that it can apply the appropriate options and figure out which other files are included in the current “project”. By default, editors powered by TypeScript’s language server do this by walking up each parent directory to find a tsconfig.json.

One case where this slightly fell over is when a tsconfig.json simply existed to reference other tsconfig.json files.

  1. json
    // tsconfig.json
  2. {
  3.   files: [],
  4.   references: [
  5.     { path: "./tsconfig.shared.json" },
  6.     { path: "./tsconfig.frontend.json" },
  7.     { path: "./tsconfig.backend.json" },
  8.   ],
  9. }

This file that really does nothing but manage other project files is often called a “solution” in some environments. Here, none of these tsconfig.*.json files get picked up by the server, but we’d really like the language server to understand that the current .ts file probably belongs to one of the mentioned projects in this root tsconfig.json.

TypeScript 3.9 adds support to editing scenarios for this configuration. For more details, take a look at the pull request that added this functionality.

Breaking Changes

Parsing Differences in Optional Chaining and Non-Null Assertions

TypeScript recently implemented the optional chaining operator, but we’ve received user feedback that the behavior of optional chaining (?.) with the non-null assertion operator (!) is extremely counter-intuitive.

Specifically, in previous versions, the code

  1. ts
    foo?.bar!.baz;

was interpreted to be equivalent to the following JavaScript.

  1. js
    (foo?.bar).baz;

In the above code the parentheses stop the “short-circuiting” behavior of optional chaining, so if foo is undefined, accessing baz will cause a runtime error.

The Babel team who pointed this behavior out, and most users who provided feedback to us, believe that this behavior is wrong. We do too! The thing we heard the most was that the ! operator should just “disappear” since the intent was to remove null and undefined from the type of bar.

In other words, most people felt that the original snippet should be interpreted as

  1. js
    foo?.bar.baz;

which just evaluates to undefined when foo is undefined.

This is a breaking change, but we believe most code was written with the new interpretation in mind. Users who want to revert to the old behavior can add explicit parentheses around the left side of the ! operator.

  1. ts
    foo?.bar!.baz;

} and > are Now Invalid JSX Text Characters

The JSX Specification forbids the use of the } and > characters in text positions. TypeScript and Babel have both decided to enforce this rule to be more comformant. The new way to insert these characters is to use an HTML escape code (e.g. <span> 2 &gt 1 </div>) or insert an expression with a string literal (e.g. <span> 2 {">"} 1 </div>).

Luckily, thanks to the pull request enforcing this from Brad Zacher, you’ll get an error message along the lines of

  1. Unexpected token. Did you mean `{'>'}` or `&gt;`?
  2. Unexpected token. Did you mean `{'}'}` or `&rbrace;`?

For example:

  1. tsx
    let directions = <span>Navigate to: Menu Bar > Tools > Options</div>
  2. //                                           ~       ~
  3. // Unexpected token. Did you mean `{'>'}` or `>`?

That error message came with a handy quick fix, and thanks to Alexander Tarasyuk, you can apply these changes in bulk if you have a lot of errors.

Stricter Checks on Intersections and Optional Properties

Generally, an intersection type like A & B is assignable to C if either A or B is assignable to C; however, sometimes that has problems with optional properties. For example, take the following:

  1. ts
    interface A {
  2.   a: number; // notice this is 'number'
  3. }
  5. interface B {
  6.   b: string;
  7. }
  9. interface C {
  10.   a?: boolean; // notice this is 'boolean'
  11.   b: string;
  12. }
  14. declare let x: A & B;
  15. declare let y: C;
  17. y = x;

In previous versions of TypeScript, this was allowed because while A was totally incompatible with C, B was compatible with C.

In TypeScript 3.9, so long as every type in an intersection is a concrete object type, the type system will consider all of the properties at once. As a result, TypeScript will see that the a property of A & B is incompatible with that of C:

  1. Type 'A & B' is not assignable to type 'C'.
  2.   Types of property 'a' are incompatible.
  3.     Type 'number' is not assignable to type 'boolean | undefined'.

For more information on this change, see the corresponding pull request.

Intersections Reduced By Discriminant Properties

There are a few cases where you might end up with types that describe values that just don’t exist. For example

  1. ts
    declare function smushObjects<T, U>(x: T, y: U): T & U;
  3. interface Circle {
  4.   kind: "circle";
  5.   radius: number;
  6. }
  8. interface Square {
  9.   kind: "square";
  10.   sideLength: number;
  11. }
  13. declare let x: Circle;
  14. declare let y: Square;
  16. let z = smushObjects(x, y);
  17. console.log(z.kind);

This code is slightly weird because there’s really no way to create an intersection of a Circle and a Square - they have two incompatible kind fields. In previous versions of TypeScript, this code was allowed and the type of kind itself was never because "circle" & "square" described a set of values that could never exist.

In TypeScript 3.9, the type system is more aggressive here - it notices that it’s impossible to intersect Circle and Square because of their kind properties. So instead of collapsing the type of z.kind to never, it collapses the type of z itself (Circle & Square) to never. That means the above code now errors with:

  1. Property 'kind' does not exist on type 'never'.

Most of the breaks we observed seem to correspond with slightly incorrect type declarations. For more details, see the original pull request.

Getters/Setters are No Longer Enumerable

In older versions of TypeScript, get and set accessors in classes were emitted in a way that made them enumerable; however, this wasn’t compliant with the ECMAScript specification which states that they must be non-enumerable. As a result, TypeScript code that targeted ES5 and ES2015 could differ in behavior.

Thanks to a pull request from GitHub user pathurs, TypeScript 3.9 now conforms more closely with ECMAScript in this regard.

Type Parameters That Extend any No Longer Act as any

In previous versions of TypeScript, a type parameter constrained to any could be treated as any.

  1. ts
    function foo<T extends any>(arg: T) {
  2.   arg.spfjgerijghoied; // no error!
  3. }

This was an oversight, so TypeScript 3.9 takes a more conservative approach and issues an error on these questionable operations.

  1. ts
    function foo<T extends any>(arg: T) {
  2.   arg.spfjgerijghoied;
  3.   //  ~~~~~~~~~~~~~~~
  4.   // Property 'spfjgerijghoied' does not exist on type 'T'.
  5. }

export * is Always Retained

In previous TypeScript versions, declarations like export * from "foo" would be dropped in our JavaScript output if foo didn’t export any values. This sort of emit is problematic because it’s type-directed and can’t be emulated by Babel. TypeScript 3.9 will always emit these export * declarations. In practice, we don’t expect this to break much existing code.

More libdom.d.ts refinements

We are continuing to move more of TypeScript’s built-in .d.ts library (lib.d.ts and family) to be generated from Web IDL files directly from the DOM specification. As a result some vendor-specific types related to media access have been removed.

Adding this file to an ambient *.d.ts to your project will bring them back:

  1. ts
    interface AudioTrackList {
  2.      [Symbol.iterator](): IterableIterator<AudioTrack>;
  3.  }
  5. interface HTMLVideoElement {
  6.   readonly audioTracks: AudioTrackList
  8.   msFrameStep(forward: boolean): void;
  9.   msInsertVideoEffect(activatableClassId: string, effectRequired: boolean, config?: any): void;
  10.   msSetVideoRectangle(left: number, top: number, right: number, bottom: number): void;
  11.   webkitEnterFullScreen(): void;
  12.   webkitEnterFullscreen(): void;
  13.   webkitExitFullScreen(): void;
  14.   webkitExitFullscreen(): void;
  16.   msHorizontalMirror: boolean;
  17.   readonly msIsLayoutOptimalForPlayback: boolean;
  18.   readonly msIsStereo3D: boolean;
  19.   msStereo3DPackingMode: string;
  20.   msStereo3DRenderMode: string;
  21.   msZoom: boolean;
  22.   onMSVideoFormatChanged: ((this: HTMLVideoElement, ev: Event) => any) | null;
  23.   onMSVideoFrameStepCompleted: ((this: HTMLVideoElement, ev: Event) => any) | null;
  24.   onMSVideoOptimalLayoutChanged: ((this: HTMLVideoElement, ev: Event) => any) | null;
  25.   webkitDisplayingFullscreen: boolean;
  26.   webkitSupportsFullscreen: boolean;
  27. }
  29. interface MediaError {
  30.   readonly msExtendedCode: number;
  31.   readonly MS_MEDIA_ERR_ENCRYPTED: number;
  32. }