Is there plan for ES Module support?

Description

Contributor guide

Tech stack

javascripthtmlcss

Domain

frontend

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

half day

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

Basic JavaScriptES modulesnpm package.json

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

30

Research direction

The issue requests ES module support for the easy markdown editor library. The discussion in the comments suggests adding an 'exports' field in package.json or using a dual CommonJS/ESM build. First, check if the maintainers are still interested by reviewing recent comments and the repository's activity. Then, examine the existing build setup (likely using webpack or rollup) and implement a strategy to output an ES module version alongside the CommonJS one. Consider using the 'type: module' in package.json or a separate .mjs file.