Why my NextJS 15 project with type:module don't require all these .js suffix ?

[nicolas-zozol]

Summary

I'm going crazy with commonJS/ESM/NodeNext rules....
So I finally decided to add .js everywhere. There is a great tool called ts2esm that makes most of the work.

Then it appears that NextJS don't care of .js extensions, even with RSC and type:module.
I guess it works on Node. Is it an old version ? Is there a flag or a trick ?

I want to understand because I don't want to release an ESM bomb to my future clients that will receive my code.

Additional information

No response

Example

No response

[bennycode]

@nicolas-zozol your issue may be related to this one: #46078

[icyJoseph]

What moduleResolution, do you have setup? (assuming you got TS installed)

[nicolas-zozol]

I have this one:

"compilerOptions": {
    "target": "ES2020",
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "jsx": "preserve",
    

[icyJoseph]

Aha, I was expecting bundler in moduleResolution. I think if you wanna do the best thing for your client, going with bundler in moduleResult is the way to go?

• https://www.typescriptlang.org/tsconfig/#moduleResolution

'bundler' for use with bundlers. Like node16 and nodenext, this mode supports package.json "imports" and "exports", but unlike the Node.js resolution modes, bundler never requires file extensions on relative paths in imports.