TypeScript 3.5 contains certain optimizations over TypeScript 3.4 for type-checking more efficiently.These improvements are significantly more pronounced in editor scenarios where type-checking drives operations like code completion lists.

TypeScript 3.5 improves on 3.4’s build mode, by saving information about how the state of the world was calculated - compiler settings, why files were looked up, where files were found, etc.In scenarios involving hundreds of projects using TypeScript’s project references in —build mode, we’ve found that the amount of time rebuilding can be reduced by as much as 68% compared to TypeScript 3.4!

For more details, you can see the pull requests to

TypeScript 3.5 introduces the new Omit helper type, which creates a new type with some properties dropped from the original.

Here we were able to copy over all the properties of Person except for location using the Omit helper.

For more details, , as well as the change to use Omit for object rest.

In TypeScript 3.4 and earlier, certain excess properties were allowed in situations where they really shouldn’t have been.For instance, TypeScript 3.4 permitted the incorrect name property in the object literal even though its types don’t match between Point and Label.

  1. type Point = {
  2.     x: number;
  3.     y: number;
  4. };
  6. type Label = {
  7.     name: string;
  8. };
  10. const thing: Point | Label = {
  11.     x: 0,
  12.     y: 0,
  13.     name: true // uh-oh!
  14. };

In TypeScript 3.5, the type-checker at least verifies that all the provided properties belong to some union member and have the appropriate type, meaning that the sample above correctly issues an error.

Note that partial overlap is still permitted as long as the property types are valid.

  1. const pl: Point | Label = {
  2.     x: 0,
  3.     y: 0,
  4.     name: "origin" // okay
  5. };

In TypeScript 3.5, you can now reference UMD global declarations like

from anywhere - even modules - using the new —allowUmdGlobalAccess flag.

This mode adds flexibility for mixing and matching the way 3rd party libraries, where globals that libraries declare can always be consumed, even from within modules.

For more details, .

In TypeScript 3.4 and prior, the following example would fail:

  1. type S = { done: boolean, value: number }
  2. type T =
  3.     | { done: true, value: number };
  5. declare let source: S;
  6. declare let target: T;
  8. target = source;
  1. interface Foo {
  2.     kind: "foo";
  3.     value: string;
  4. }
  6. interface Bar {
  7.     kind: "bar";
  8.     value: number;
  9. }
  11. function doSomething(x: Foo | Bar) {
  12.     if (x.kind === "foo") {
  13.         x.value.toLowerCase();
  14.     }
  15. }
  17. // uh-oh - luckily TypeScript errors here!
  18. doSomething({
  19.     kind: "foo",
  20.     value: 123,
  21. });

However, this was a bit overly strict for the original example.If you figure out the precise type of any possible value of S, you can actually see that it matches the types in T exactly.

In TypeScript 3.5, when assigning to types with discriminant properties like in T, the language actually will go further and decompose types like S into a union of every possible inhabitant type.In this case, since boolean is a union of true and , S will be viewed as a union of { done: false, value: number } and { done: true, value: number }.

For more details, you can see the original pull request on GitHub.

In TypeScript 3.4, we improved inference for when generic functions that return functions like so:

took other generic functions as arguments, like so:

  1. function arrayify<T>(x: T): T[] {
  2.     return [x];
  3. }
  4. type Box<U> = { value: U }
  5. function boxify<U>(y: U): Box<U> {
  6.     return { value: y };
  7. }
  9. let newFn = compose(arrayify, boxify);

Instead of a relatively useless type like (x: {}) => Box<{}[]>, which older versions of the language would infer, TypeScript 3.4’s inference allows newFn to be generic.Its new type is <T>(x: T) => Box<T[]>.

TypeScript 3.5 generalizes this behavior to work on constructor functions as well.

  1. class Box<T> {
  2.     kind: "box";
  3.     value: T;
  4.     constructor(value: T) {
  5.         this.value = value;
  6.     }
  7. }
  9. class Bag<U> {
  10.     kind: "bag";
  11.     value: U;
  12.     constructor(value: U) {
  13.         this.value = value;
  14.     }
  15. }
  18. function composeCtor<T, U, V>(
  19.     F: new (x: T) => U, G: new (y: U) => V): (x: T) => V {
  21.     return x => new G(new F(x))
  22. }

To learn more, .