diff --git a/packages/documentation/copy/en/reference/Modules.md b/packages/documentation/copy/en/reference/Modules.md index 9cb5e3589708..501e740eb423 100644 --- a/packages/documentation/copy/en/reference/Modules.md +++ b/packages/documentation/copy/en/reference/Modules.md @@ -141,9 +141,12 @@ import { APIResponseType } from "./api"; // Explicitly use import type import type { APIResponseType } from "./api"; + +// Explicitly pull out a value (getResponse) and a type (APIResponseType) +import { getResponse, type APIResponseType} from "./api"; ``` -`import type` is always guaranteed to be removed from your JavaScript, and tools like Babel can make better assumptions about your code via the [`isolatedModules`](/tsconfig#isolatedModules) compiler flag. +Any explicitly marked `type` import is guaranteed to be removed from your JavaScript, and tools like Babel can make better assumptions about your code via the [`isolatedModules`](/tsconfig#isolatedModules) compiler flag. You can read more in the [3.8 release notes](https://devblogs.microsoft.com/typescript/announcing-typescript-3-8-beta/#type-only-imports-exports). ## Default exports diff --git a/packages/tsconfig-reference/copy/en/options/moduleResolution.md b/packages/tsconfig-reference/copy/en/options/moduleResolution.md index bcaf9722b490..0287f4dec367 100644 --- a/packages/tsconfig-reference/copy/en/options/moduleResolution.md +++ b/packages/tsconfig-reference/copy/en/options/moduleResolution.md @@ -6,7 +6,7 @@ oneline: "Specify how TypeScript looks up a file from a given module specifier." Specify the module resolution strategy: - `'node'` for Node.js' CommonJS implementation -- `'node12'` or `'nodenext'` for Node.js' ECMAScript Module Support [from TypeScript 4.5 onwards](https://devblogs.microsoft.com/typescript/announcing-typescript-4-5-beta/) +- `'node16'` or `'nodenext'` for Node.js' ECMAScript Module Support [from TypeScript 4.7 onwards](https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/#esm-nodejs) - `'classic'` used in TypeScript before the release of 1.6. You probably won't need to use `classic` in modern code There is a handbook reference page on [Module Resolution](/docs/handbook/module-resolution.html)