David Lorenz

@swyftx-simon Actually, since this turned to show more problems the more "workarounds" we tried to add , we had a large discussion and there are only 3 things I can...

> https://github.com/vercel/next.js/issues/39375#issuecomment-1208109442 > So if no .mjs are found (even though type = module , or 'import' is defined, it will always treat the package as cjs? Our research would...

I've done a bit more research on this and since the error is being triggered with this error log ``` ModuleJob._instantiate node:internal/modules/esm/module_job (124:21) async ModuleJob.run node:internal/modules/esm/module_job (190:5) ``` I have...

According to https://nodejs.org/api/esm.html `.mjs` is the proposed format and it seems to hit confusion in combination with `exports: `. Which, when type isn't explicitly `module`, currently (node 16,18,19) won't resolve...

Alright. I've researched this for quite some while now. What I reported above seems to hold true. Now for people searching for a **SOLUTION** only I have exactly 2 proposals...

> For reference. Adobe reverted their update to .mjs recently. > > [adobe/react-spectrum#3630](https://github.com/adobe/react-spectrum/pull/3630) Well, there's just standard people working everywhere. But with revert you mean `.js` to `.mjs` or not?...

> Is `tsconfig.js` make sure `moduleResolution` is set to `node16` Too few information: When does this help and where? Are you suggesting to set `moduleResolution: node16` in the project (NextJS...

This bug misses a complete description. It's not possible to follow up what you mean. Please add "steps to reproduce" accordingly. It's not clear what is not working, it's not...

@MildTomato please close.

I don't wanna stress but just saying: having this merged would be 0 to 100 awesome