Resolve .tsx files from .js extensions

[karlhorky]

Ref: #1 (comment)

[lukeed]

TypeScript doesn't allow imports to *.jsx files right?

[karlhorky]

tsc allows both:

• .jsx to resolve .tsx
• .jsx to resolve .ts

edit: oh wait, did you mean .js resolving to .jsx? ...that doesn't work.

[karlhorky]

Should we add the other transforms for .jsx import paths too?

[lukeed]

No @ jsx updates – that's ridiculous

Please check out the CI results for the test-tsx branch – it replicates your original issue and yet the jsx and tsx files are loaded correctly regardless of the sourcefile's extension and ESM-vs-CJS format.

Edit: It doesn't replicate your issue at all 🙈 lol 😴

[lukeed]

Can you actually send over a reproduction using ts-node? I can get tsc to not throw errors, but ts-node never actually works or applies any of the resolutions described here or in my updated test files

[karlhorky]

Can you actually send over a reproduction using ts-node?

Sure, here's a Replit: https://replit.com/@karlhorky/SuperbLivelyEditor#index.ts

The start script runs ts-node-esm index.ts

[karlhorky]

@lukeed just circling back around to this since I noticed a new version of tsm was released.

What do you think about getting a fix in for the inconsistency with the .js fully-specified ESM import paths?

[karlhorky]

Did some more research on what tsc and esbuild supports for extensions over here, also including the latest nodenext options in tsconfig.json:

privatenumber/tsx#112 (comment)

[karlhorky]

Nice, [email protected] (PR #43) is working, thanks! 🙌