TypeScript 3.8 unveils new syntax for type-only imports

Fixing current issues with JavaScript import syntax, the next version of TypeScript will provide more fine-grained control over imports and elisions

Comments

TypeScript 3.8, a new version of Microsoft’s typed superset of JavaScript, is now available in a beta release. The latest TypeScript upgrade emphasizes type-only imports and exports and ECMAScript standards compliance.

The release adds a new syntax for type-only imports and exports, with the intent of giving users more fine-grained control over import and elision. The import type syntax only imports declarations to be used for type annotations and declarations and always gets fully erased. The export type syntax only provides an export to be used for type contexts and is erased from TypeScript output.

TypeScript has used JavaScript’s import syntax to enable reference types. While convenient, the capability only worked because of the import elision feature, which omits TypeScript type imports when TypeScript outputs JavaScript files. However, import elision has been both insufficient and problematic.

In conjunction with import type, TypeScript 3.8 also adds a compiler flag to control what happens with imports that won’t be used at runtime: importsNotUsedAsValues.

Regarding the ECMAScript standard for JavaScript, TypeScript 3.8 adds support for ECMAScript private fields, which is part of a class fields declaration proposal for JavaScript. Public and private fields will be integrated into single, orthogonal whole, according to this proposal.

Other improvements planned for TypeScript 3.8 include:

Implementation of the export as * ns syntax, providing a single entry point to expose all members of another module as a single member.
Top-level await, an upcoming ECMAScript feature to remove restrictions on using an await expression at the top of a file under specific conditions.
JavaScript files are supported in TypeScript 3.8 by turning on the allowJs flag; type-checking of those files is supported via the checkjscode option or by adding a // @ts-check comment to the top of .js files. New JSDoc tags are leveraged for properties, because JavaScript files lack a dedicated syntax for type-checking.
A watchOptions field in tsconfig.json and jsconfig.json lets users tell the compiler/language service which file watching strategies to use to keep track of files and directories.