4 ms·
There's a "dedicated thread" on the question here https://github.com/nodejs/loaders/issues/214 https://github.com/nodejs/loaders/issues/214 There are about 100
by pas 2y ago
There's a "dedicated thread" on the question here https://github.com/nodejs/loaders/issues/214 https://github.com/nodejs/loaders/issues/214
There are about 100 messages in the comments on the linked PR all about the import extensions compatibility/consequences :)
There's a "roadmap doc" here https://github.com/nodejs/loaders/issues/217 https://github.com/nodejs/loaders/issues/217 that states "No .js extension for .ts files."
> I'd prefer it break existing code to enforce correctness
That seems to be the goal and intent (from TS and Node team too https://github.com/nodejs/node/pull/53725#issuecomment-2230113189 https://github.com/nodejs/node/pull/53725#issuecomment-22301... )
> Will it transform esm import syntax into require statements?
IIUC no
see the docs about which module system Node picks for the loaded files https://github.com/nodejs/node/blob/main/doc/api/typescript.md#type-stripping https://github.com/nodejs/node/blob/main/doc/api/typescript.... ("Node.js will not convert from one module system to another")