Fix: use named exports only for ESM build

[benmccann]

Marked version: 3.0.6

Markdown flavor: all

Description

• Fixes issue described here: Expose named exports for ESM build #2223 (comment)

Expectation

UMD build should have only default export for backwards compatibility. CJS cannot have both named and default exports like ESM can

Result

Backwards compatibility broke in UMD build

Contributor

• Test(s) exist to ensure functionality and minimize regression (if no tests added, list tests covering this PR); or,
• no tests required for this PR.
• If submitting new feature, it has been documented in the appropriate places.

Committer

In most cases, this should be a different person than the contributor.

• CI is green (no forced merge required).
• Squash and Merge PR following conventional commit guidelines.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/markedjs/markedjs/7hqcLD8XkkvDd67KoNgefVcPbU9B
✅ Preview: https://markedjs-git-fork-benmccann-esm-entry-markedjs.vercel.app

[UziTech]

Thanks for working on this.

[benmccann]

No problem. Sorry I broke things

[UziTech]

Happens to all of us ☺️

[ddolcimascolo]

Hi guys, do you plan to release a patched version soon?

Thx,
David

[RomanHotsiy]

@UziTech @styfle could you please cut a new release 🙏. This breaks our customer builds.

[github-actions]

🎉 This PR is included in version 3.0.7 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[ddolcimascolo]

Thx