no longer bundle promise shim
Open
Nobody has claimed this yet.
browser
bug
- Dominant language
- JavaScript
- Stars
- 17k
- Forks
- 3.4k
- Avg merge
- 7h 42m
- Merged PRs (30d)
- 26
Description
We no longer need the consumer to have promises - people can use the promises implementation or not.
Maybe we should remove the polyfill and then if its not there, make sure it doesn't complain unless you ask less for a promise (and there is no browser Promise)
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
No file, test, or entry point is named in the issue. Start by locating the bundled Promise polyfill and the code that checks for a browser Promise; determine how consumers can opt into a Promise implementation and what behavior is expected when none is available. Done means the unnecessary polyfill is removed without complaints unless Promise-dependent functionality is requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100