Skip to content

FAQ on module specifier rewriting is outdated #62705

@valler

Description

@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.

Metadata

Metadata

Assignees

Labels

DocsThe issue relates to how you learn TypeScript

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions