Execute polyfills et al before application code
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 32
- Forks
- 17
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 4
Description
Right now, if you use Object.entries outside of a class or function definition in one of our application js files (eg: static/js/containers/ProfilePage.js), you'll get a error claiming that 'Object.entries is undefined'. We should figure out a way to run the polyfill code (and any other such global setup) before the code in our application js files
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 with static/js/containers/ProfilePage.js and inspect how polyfills or other global setup currently load relative to application code. Reproduce the Object.entries failure at module scope, then verify that polyfills run first and the example application code no longer reports Object.entries as undefined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100