micromatch / micromatch/picomatch
TypeScript and ESM plans
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.3k
- Forks
- 135
- Avg merge
- 23h 38m
- Merged PRs (30d)
- 7
Description
Hi! Would you be open to moving picomatch to TypeScript and making the package ESM only in the next major version?
I found the earlier discussions in #108 and #109, as well as the more recent ESM PR in #152, but I didn’t see a clear decision. TypeScript types were also discussed in #18 and #53.
What I have in mind is TypeScript source, ESM output, and types shipped with the package. I know TypeScript would add a build step, unlike the approach in #152, so I wanted to ask before working on anything.
Is this something you’d be interested in? If so, would you rather land ESM first and consider TypeScript later, or do both in the same major release?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the earlier discussions in #108, #109, #18, and #53, along with the ESM pull request in #152. The immediate outcome is a maintainer decision on whether to adopt TypeScript, ESM-only output, or both in the next major release; implementation files and tests are not identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100