fixed an error using import syntax when the moduleResolution field is nodeNext in tsconfig.json

[mlgq]

This is an awesome project! It helped me a lot with the work I was doing.

type: "module" in package.json is necessary for local development, but not useful for online package. Also using import syntax when the moduleResolution field in tsconfig.json is nodeNext results in an error.

This PR uses npm hooks to remove the type field in package.json before the package is published, and leave the locally development code unchanged.

[fabiosantoscode]

This is an ESM package with a CJS backup (dist/bundle.min.js) for older node versions. Removing "type": "module" makes it just CJS!

So I can't accept this approach, but I want to understand what the problem was.

Is it the case that typescript's nodeNext finds this setup too weird? After all, there's a sub-package just for bundle.min.js.

[mlgq]

Removing "type": "module" makes it just CJS!

Okay, I'm wrong brother. I focused on Typescript but ignored Node. Although this field causes a ts error, but it can be blocked by @ts-ignore

[mlgq]

done