27 ms·
Agree completely. It also makes interop between Node and Deno more painful. But there is hope on the horizon. :) See https://github.com/microsoft/TypeScript/is
by lewisl9029 4y ago
Agree completely. It also makes interop between Node and Deno more painful. But there is hope on the horizon. :)
See https://github.com/microsoft/TypeScript/issues/37582 https://github.com/microsoft/TypeScript/issues/37582 which is referenced in the 4.9 Iteration Plan as "Support .ts as a Module Specifier for Bundler/Loader Scenarios": https://github.com/microsoft/TypeScript/issues/50457 https://github.com/microsoft/TypeScript/issues/50457
- codefined 4y agoActually looks to be tabled for TypeScript 5.0, release date of 'March 14th' next year.
- cypress66 4y agoBut that doesn't seem like it would fix the typical flow, there still would be no transpiling of imports. So yes you could use .ts in ts-node, but you would have to use .js in tsc. Which is pretty awful (you want your code to work with both).