Is your feature request related to a problem? Please describe.
In node.js 23 we have --experimental-strip-types now which allows us to run .ts files directly (with some limitations) and import .ts files directly.
With emitLegacyCommonJSImports set to true we get .js extension, but there is no configuration possible to get .ts extension.
Describe the solution you'd like
An alternative configuration options that would allow having .ts extension. It could be full-control like "customExtension" or just a simple enum of 3 (none, js, ts).
Describe alternatives you've considered
As an alternative today we have to "pre-build" typescript before running node.js, which has worked fine since forever but would be cool if we could skip this step.
Is your feature request related to a problem? Please describe.
In node.js 23 we have
--experimental-strip-typesnow which allows us to run.tsfiles directly (with some limitations) and import.tsfiles directly.With
emitLegacyCommonJSImportsset totruewe get.jsextension, but there is no configuration possible to get.tsextension.Describe the solution you'd like
An alternative configuration options that would allow having
.tsextension. It could be full-control like "customExtension" or just a simple enum of 3 (none, js, ts).Describe alternatives you've considered
As an alternative today we have to "pre-build" typescript before running node.js, which has worked fine since forever but would be cool if we could skip this step.