From c66e76904ed529d26a3eda18a61314b0b033891a Mon Sep 17 00:00:00 2001 From: Matt Kantor Date: Mon, 8 Dec 2025 11:56:41 -0800 Subject: [PATCH] Clarify module specifier rewriting Mention `rewriteRelativeImportExtensions`. --- FAQ.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/FAQ.md b/FAQ.md index 7fe13e54..9c5695bf 100644 --- a/FAQ.md +++ b/FAQ.md @@ -57,7 +57,7 @@ It's explicitly out of scope for TypeScript to modify module specifiers as they import x from "some/path"; ``` -the output specifier *will always be* `"some/path"` regardless of your tsconfig settings. +the output specifier *will always be* `"some/path"` regardless of your tsconfig settings (with the exception of [`rewriteRelativeImportExtensions`](https://www.typescriptlang.org/tsconfig/#rewriteRelativeImportExtensions)). This includes things like changing file extensions, changing `paths` lookups to their resolutions, changing absolute paths to relative paths, changing relative paths to absolute paths, changing sub-module specifiers to something else, and so on. The string in the import path is the string in the emitted JavaScript, no exceptions.