tsconfig's allowImportingTsExtensions and the transpilation result - is there a way to set imported .ts to .js?

[mkvlrn-cm42]

I'm not even sure if this is a good practice now or not, but I've just only found out about allowImportingTsExtensions in tsconfig.json, which allows me to import my esm modules using .ts instead of .js, which makes a bit more sense during development.

So when transpiling with swc the resulting js files keep the imports as .ts.

Is there a setting in the cli or .swcrc that also transforms the extension of the imports from .ts to .js?

[kdy1]

Search for resolveFully in the docs. It's jsc.module.resolveFully

[alshdavid]

@mkvlrn, you're a legend! Thank you 🙏

[falkenhawk]

Thanks @mkvlrn ! But it seems @swc/plugin-transform-imports does not handle dynamic imports (await import('foo.ts')) either... 😭

[mkvlrn-cm42]

@falkenhawk I have a similar issue when using Workers that need to have a file name used instead of importing something the "usual" way, and I settled with doing some trickery:

const extension = import.meta.url.split(".").pop();
const worker = new Worker(`my-worker.${extension}`);

Works beautifully in my case, maybe you can use that as a starting point?

[lukakostic]

Search for resolveFully in the docs. It's jsc.module.resolveFully

module.resolveFully = true does nothing, import extensions remain .ts.

Suggested answer is using @swc/plugin-transform-imports , why must we resort to plugins? Why not always transform .ts to .js if target is es ?

[kdy1]

You don't need a plugin anymore. #9784