Is this project dead from community??
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 145
- PR merge metrics
- No merged PRs in 30d
Description
Node native ESM spec is not applied and this is causing a lot of compatibility issues, when I use pure ESM, I have to enable importHelpers: false because tslib's configuration is invalid.
https://github.com/microsoft/tslib/issues/170
https://github.com/microsoft/tslib/issues/173
https://github.com/microsoft/tslib/issues/161
Why you maintainers can't see these?? What the resistance stopping you from fixing them?
There are a few PRs fixing those issues but received no feedback, it's just disappointing.
cc @DanielRosenwasser @orta @rbuckton @ExE-Boss
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 by reading the three linked tslib issues (#170, #173, and #161) and inspecting the referenced pull requests, since no file or test is named. Determine which Node native ESM compatibility and configuration problems remain unresolved; done requires a defined scope and verification that pure ESM no longer requires importHelpers: false.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100