FAQ on module specifier rewriting is outdated

[valler]

Acknowledgement

• I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

Comment

https://github.com/microsoft/TypeScript/wiki/FAQ#module-specifier-rewriting

states that:

It's explicitly out of scope for TypeScript to modify module specifiers as they appear in emitted JS, e.g. if you write

import x from "some/path";

the output specifier will always be "some/path" regardless of your tsconfig settings.

This is no longer true since 5.7 with the introduction of rewriteRelativeImportExtensions.

[RyanCavanaugh]

🤖 This is an automated response. I looked for things that might help (duplicates, FAQ entries, etc) but didn't find anything. A human will take a look!