timers-browserify dependency on setimmediate pollutes global environment
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, webpack
- Domain
- build-system, frontend
Research direction
Start by tracing how the setimmediate dependency is included in timers-browserify and reproduce the behavior in a Webpack build. Check whether setImmediate and clearImmediate become globals, then verify the chosen behavior no longer pollutes the consuming page while preserving the timers API.
Written by the indexing model from the issue text.
Description
timers-browserify depends on setimmediate to make available setImmediate and clearImmediate functions.
This breaks proper encapsulation in Webpack builds where we don't want to pollute the global environment with polyfills. E.g. when authoring drop-in widgets for use within someone else's website and acting as a third-party.
- Dominant language
- JavaScript
- Stars
- 24
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·