fix: TS1479 error

[dilame]

Fixes #756.

Key Change:

• Addition of "type": "module" in package.json.

Issue Background:

• The problem arises due to TypeScript's reliance on the package.json type field to determine the module format (CommonJS or ECMAScript Module, ESM) of a project.
• In the absence of the type field, TypeScript, along with Node.js, defaults to interpreting modules as CommonJS. This becomes an issue when dealing with .d.ts files, as they do not specify the module system (like .mjs or .cjs would).
• Consequently, when an ESM is imported in such a scenario, TypeScript incorrectly assumes it to be a CommonJS module, leading to module resolution conflicts described in error TS1479: The current file is a CommonJS module whose imports will produce 'require' calls #756.

Thank you for considering this pull request!

[oliverjohns]

Ivan Hofer passed away. Im not sure there is any one that can approve this PR

[timofei-iatsenko]

Actually, it's incorrect solution as well.

Read more here:

• Generate index.d.mts and index.d.cts unjs/unbuild#238
• https://twitter.com/atcb/status/1634653474041503744
• NodeNext resolution failed to resolve dual-package correctly microsoft/TypeScript#50466