[TS] Use "moduleResolution": "bundler" in tsconfig ?

[goswinr]

How about using
"bundler" instead of "node" in "moduleResolution": ?
here:

Fable/src/fable-library-ts/tsconfig.json

Line 32 in 85ed8bf

"moduleResolution": "node", /* Specify how TypeScript looks up a file from a given module specifier. */

"node" seems deprecated in TS 6:

Along with that change, I would also remove all .ts suffixes from relative imports in fable-library-ts

Otherwise, users always have to put "allowImportingTsExtensions": true in their tsconfigs.
Or is that not a good idea for some reason?

[MangelMaxime]

Along with that change, I would also remove all .ts suffixes from relative imports in fable-library-ts

We keep going back and forth regarding that point...

In the past we were using .js which was the recommended (kind of way) of doing it from TS I believe. However, some tools like Deno expects users to use .ts extensions in the import.

Related discussion can be found here:

• The TypeScript file generated by Fable tries to import a file with a .js extension that does not exist #3686
• Typescript imports have wrong file extension #3973

I don't know what the effect of this moduleResolution do, but does it means we could avoid having .js or .ts extension in relative imports? And if yes, we need to check if this works for Deno too.