microsoft / microsoft/TypeScript-Website
Add `exports` map to `package.json` of `@typescript/twoslash`
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 7
Description
I wanted to know if you'd be open to a PR for this. Twoslash distributes an ESM version, but there's no way to use it from Node.js since exports is not defined. We need to use the ESM version as some of our tooling is having issues with encountering a require
Contributor guide
No contributing guide indexed for this repository
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 at the package.json for @typescript/twoslash and review how its ESM distribution is currently exposed to Node.js. Done means the published package provides an exports map that lets Node.js consumers use the ESM version without encountering require; no test file is mentioned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100