max-mapper / max-mapper/concat-stream
Drop polyfills in a next semver major?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 574
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
Would you be open to a PR that bumps minimum supported version and gets rid of the polyfills, to make the library more lightweight and suitable for the modern runtime environments?
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
The issue does not name any files, tests, supported runtime version, or specific polyfills to inspect. First clarify the minimum version and the scope of the proposed semver-major change with maintainers; done would mean an agreed runtime baseline and removal of the corresponding polyfills without breaking supported environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100