Types are not correct for native ESM modules and cannot be imported there

[spence-s]

https://arethetypeswrong.github.io/?p=eslint-define-config%401.23.0

It is impossible to import types correctly into a node.js project using

"module": "node16",
"moduleResolution": "node16",

v1.20 is the last version that worked correctly

[spence-s]

I believe you just need to update the module in this tsconfig to Node16, I am happy to contribute this fix if it would be accepted. I think it would still work in the same way it does now, except it will also work in native node ESM environments where it does not now.

[Shinigami92]

Please check v1.24.1
Since v1.24 we switched from no process step to tsup bundle
So the dist content is now newly organized

If this still happens please create a minimal reproduction that we can checkout to see the error

[spence-s]

Yes this release has fixed the issue for me and you can see that it now passes more checks here:

https://arethetypeswrong.github.io/?p=eslint-define-config%401.24.1

The website linked is maintained by TS or a core TS maintainer, and has been really helpful for me to understand the complex modules system and fix inconsistencies.

https://github.com/arethetypeswrong/arethetypeswrong.github.io/tree/main/packages/cli

Thanks for the fix!