(feat) support node16/nodenext

[dummdidumm]

#1522

Not sure how to test this, I thought that this would error if I leave out .js in imports but that's not the case, so I'm not sure if this is actually working. @jasonlyu123 @JuanM04 do you know more? Edit: Turns out that was an error on our part, we need to pass a new parameter to resolveModuleNames in the TypeScript plugin.

@JuanM04 would be great if you could test this out:

1. Check out this branch
2. Make sure you have yarn 1.x
3. yarn install
4. yarn bootstrap
5. go in language-server and run yarn build
6. go in svelte-check and run yarn build
7. copy over dist folder into your project (replace the dist folder of your existing svelte-check in your node_modules)

[JuanM04]

I tried it in my project where I first saw the bug and it seems to work!

[dummdidumm]

Great to hear that! Was the bug around not respecting the exports map of a package? What I'm still confused about is that I don't seem to get errors from TS about missing file endings (.js) from relative imports

[JuanM04]

Was the bug around not respecting the exports map of a package?

Yes, that's how I've spotted it. In fact, I have a dependency with broken exports and now svelte-check detects it.

What I'm still confused about is that I don't seem to get errors from TS about missing file endings (.js) from relative imports

Maybe svelte2tsx has something to do with it?

[dummdidumm]

Mhm we might need to also check the resolution mode, as implemented here TypeStrong/ts-node#1778 and exposed since 4.7 (microsoft/TypeScript#49360). Edit: Yep that fixes the "no errors for missing .js extension" problem.