Karl Horky

Hmm... as a workaround in the meantime, would it be possible to create a map of `./file.js` to `./file` module file paths using something like [the `NormalModuleReplacementPlugin`](https://webpack.js.org/plugins/normal-module-replacement-plugin/)? 🤔

The problem is that using the fully-specified `.js` extension fails when using TypeScript `.ts` files (they are not resolved in parity with the behavior of TypeScript and `tsc`) With TypeScript...

Maybe somewhat related, although it seems this person is describing the opposite: they want to write node-style specifiers (without the extension) and have them resolved to the `.js` files (ignoring...

> I think in ts better to have `ts` extension at the end, it is fully-specified import The TypeScript team doesn't agree, check out the issue I linked above: https://github.com/microsoft/TypeScript/issues/41887#issuecomment-741968855

Thanks for the confirmation, I've opened an issue in `babel-loader` over here: https://github.com/babel/babel-loader/issues/904

not stale

Ok so @alexander-akait can I assume by closing this, it means that it will be implemented over in `ts-loader` in that issue https://github.com/TypeStrong/ts-loader/issues/1383 ? That means that it will no...

@sokra did you have a chance to make a decision here? Should this be in webpack core as you [suggested above](https://github.com/webpack/webpack/issues/13252#issuecomment-828714153)? Or should this be done in `ts-loader`, potentially as...

Oh great, good news, thanks for the update! So am I understanding correctly: this is already implemented in `enhanced-resolve` and now just needs to be implemented in `ts-loader`?

**Edit:** Jest 28 no longer has this issue: https://github.com/adaltas/node-csv/issues/323#issuecomment-1112595978 --- Version `6.0.5` is also throwing an error with [Jest 27 Experimental ESM support](https://jestjs.io/docs/ecmascript-modules) + Node v16.11.0 (ESM): **`package.json`** ``` {...