Bug: type issue in ts@4.8+ with esm

[Mister-Hope]

Description

The package is shipping esm files, but package.json is declaring "type": "commonjs" by mistake

So typescript will assume users are importing a commonjs module, so it will report issues with:

import memaid from "memaid";

memaid.someAPI(...args)

Saying the expression is not callable.

That's because a cjs module will have it's module.exports on default key, so:

import memaid from "memaid";

memaid.default.someAPI(...args)

is ok to typescript, but it's not acually working (because we do have esm modules using export default) and the default key does not exisit.

Steps to reproduce

Create project with "type": "module" and install mermaid. then ensure ts.config.json has target: "ESxxx", you will get issues mention above. (Does not need to use moduleResolution: NodeNext)

Screenshots

No response

Code Sample

No response

Setup

No response

Additional Context

No response

[aloisklink]

Potentially a duplicate of #3799

Although that one is explicitly about using dynamic import() in CommonJS, which is a bit more complicated in TypeScript.