enhance: support tsconfig esmodule interop

[huozhi]

description

related to #531
when there's multiple exports in the source file while esModuleInterop specified as true in tsconfig compilerOptions, let rollup add __esModule: {value: true} mark to the output.

it will benefits the esmodule usage with the dist file when the dist is resolved to commonjs assets. the reason could be:

• only main field is existed in package.json
• due to some reason cjs assets is resolved instead of esmodule assets.

changes

• respect esModuleInterop in tsconfig (for typescript source only)

[changeset-bot]

⚠️ No Changeset found

Latest commit: bff8eb8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[wardpeet]

I wonder if we should add interop for non esm modules and look at rollup/rollup#3710 perhaps instead?

[huozhi]

@wardpeet ty, I'll look for other ways to workaround