Allow allowImportingTsExtensions
to be set in any module resolution mode
#52230
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When #51669 landed,
bundler
was the only module resolution mode capable of resolving TS files via.ts
-extensioned imports. But since #51435 was merged, every module resolution mode resolves these imports, so there’s no reason to predicateallowImportingTsExtensions
on module resolution mode anymore. In fact, allowing.ts
-extensioned imports can be useful in--moduleResolution nodenext
for users who are targeting Node with a TypeScript-transpiling loader like https://github.com/esbuild-kit/esm-loader.