Fix missing paths when using typescript's module nodenext feature

[IgnusG]

This resolution requires relative/mapped import paths to end with .js
This PR detects if a path ends with .js and if so adds more extension type paths to try, that omit this extension when attaching additional extensions to match the actual existing files.

Reference https://devblogs.microsoft.com/typescript/announcing-typescript-4-5-beta/#esm-nodejs

Should resolve #213 (edit 1: wrong issue sorry, edit 2: actually I believe this might resolve that issue as well) & aleclarson/vite-tsconfig-paths#59

[WoodyWoodsta]

Is this going anywhere?

[aleclarson]

Can you copy over the test from #213 ?

[WoodyWoodsta]

I would also like to know if this handles .mjs files, which is what is emitted by the TS compiler when files are .mts files.

[aleclarson]

I would also like to know if this handles .mjs files, which is what is emitted by the TS compiler when files are .mts files.

Good catch. There should definitely be a test for that.

[IgnusG]

I'll add both tests and check the mjs support 👍

[IgnusG]

I would also like to know if this handles .mjs files, which is what is emitted by the TS compiler when files are .mts files.

@WoodyWoodsta can you please check if 39354fb works for you? I barely remember this PR so I just quickly wrote down a test for it

[WoodyWoodsta]

I'm coming here from aleclarson/vite-tsconfig-paths#54, so I would need to fiddle around to test it - but will do if I manage to find a gap.

[IgnusG]

@jonaskello could you please take a look through this when you have the time?

[IgnusG]

For anyone wanting to use this in the meantime with yarn add this resolution to your package.json

{
  "resolutions": {
    "tsconfig-paths": "github:ignusg/tsconfig-paths@dev"
  }
}

[datner]

Hey, this pr was thoroughly tests, reviewed, and even approved!
This is great work and an important step in moving to full esm.

Is there a reason why this isn't merged?

[jonaskello]

Yes, seems like this change has enough tests so let's merge it.