default export of `cosmiconfig-typescript-loader` not working in esm

[mikaelkaron]

Description

As mentioned in downstream issues in graphql-codegen and graphql-config it looks like loading cosmiconfig-typescript-loader default export is buggy in esm.

What went wrong?

The error is exposed when trying the latest esm example in graphql-codegen.

• fetch local copy of https://github.com/dotansimha/graphql-code-generator/tree/master/examples/typescript-esm
• runnpm run codegen`

What did you expect should have happened?

Execution without error

What was the config you used?

Nothing except what's available in the example.

What stacktrace or error messages did you see?

loadTs is not a function

This is caused by default import of cosmiconfig-typescript-loader and later export of loadTs

Similar or dependent issues:

A lot of other packages have the same problems with esm and there's a temporary fix in the default-import package that also adds a few related issues:

• NextJS
  • Lack of ESM entry-points prevents correct default import resolution vercel/next.js#30402
  • CJS -> ESM interoperability for imports inside external modules loaded from CDN vercel/next.js#32213
• Styled Components
  • Provide styled as a named export styled-components/styled-components#3437
  • Provide better ESM support for importing styled in node styled-components/styled-components#3601
• Typescript
  • TypeScript module "Node16" does not resolve types of CJS module microsoft/TypeScript#49160 (comment)

Additional Data

Version of cosmiconfig-typescript-loader you're using:

3.1.1

Node Version:

18.4

Operating System:

Windows

[charlypoly]

@mikaelkaron The maintained version lives here: https://github.com/Codex-/cosmiconfig-typescript-loader/

[mikaelkaron]

Ok. I guess I’ll file a bug there to. Thanks @charlypoly