No named exports found in module refer to mjs file

[lwr]

ref #2093 standard/standard#863

// File a.mjs
export const A = 'a'

// File b.js
export * from './a.mjs'

// File c.js
export * from './b.js'

eslint c.js
# output
#  1:15  error  No named exports found in module './b.js'  import/export

eslint c.js --ext .js,.mjs
# output
#  1:15  error  No named exports found in module './b.js'  import/export

only renaming a.mjs to a.js can workaround this problem

[ljharb]

Do you have .mjs in the import/extensions setting? That seemed to be the fix for #2093.

[lwr]

Do you have .mjs in the import/extensions setting? That seemed to be the fix for #2093.

mjs is the official extension for modules in NodeJS, so I think that it should be parsed by default without any addition config

[ljharb]

That's true, but it can't happen until resolve supports "exports".

[Derranion]

I can confirm that this issue is still exists - got it recently with .ts files.

Here is another good example.

Would love to see it fixed because import \ export check is pretty important.
( as a workaround for now you could change rule to throw warning instead of error )

Thanks a lot.