popcodeorg / popcodeorg/popcode
Load modern ES bundle in modern browsers
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 191
- Forks
- 143
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 5
Description
It seems to be becoming fairly common practice to generate two versions of an application’s JavaScript bundle: one that retains most of the features and syntax of modern JavaScript, and a second that compiles down to pure ES5 for maximum compatibility. There’s a slightly hacky but ultimately quite simple way to make sure the right bundle flavor is loaded, by using <script type="module"> and nomodule respectively.
We should explore setting things up this way in Popcode. I think it would mostly be worth the extra complexity if the modern JS bundle were substantially smaller than the legacy bundle, so worth investigating that first.
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 reviewing the issue and the linked module/nomodule reference, then inspect how Popcode currently produces and loads its JavaScript bundles. Compare the sizes and browser compatibility of modern and ES5 output; the work is complete when the benefit is established and a concrete implementation path is documented or adopted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100