fix: ignore export assign cannot be used in module TS error, fixes #1018

[ghiscoding]

fixes #1018

Summary

Fixes issue #1018 by simply ignoring the TypeScript error since the TS error has no negative effect whatsoever on the functionality of these types. This makes TypeScript and "Are the Types Wrong" both happy and everything is back to normal and we can get back to work (finally).

The quick explanation is that sometime even when using ESM imports, CJS types exports get picked up (depending on the users tsconfig module resolutions) and export = ... is a TypeScript error, but we can easily patch it by ignoring it.

Background & Context

I found this article Default exports in CommonJS libraries which explains why export = _default was patched in the first place. However this gives a TypeScript error in some cases (depending on your tsconfig module resolutions and other configs), this error can simply be ignored altogether because the types still work correctly, the error when active though will block a TypeScript build, however simply ignoring the error will let us continue with our build successfully.

Tasks

I simply modified the existing fix-cjs-types.js script and ran a build.

This also keeps "Are the Types Wrong" happy since nothing really changed for the types themselves, so all is good and we're all happy 🎉

Dependencies

• Resolved dependency
• Open dependency

[ghiscoding]

@reduckted could you review the PR?

[reduckted]

Looks good. Thanks for investigating and finding a fix! ❤️

[cure53]

Thanks everyone!