https://github.com/JoviDeCroock/POC-ModularLegacyBuild

Module-nomodule implementation that has grown to more than just a POC
https://github.com/JoviDeCroock/POC-ModularLegacyBuild

Last synced: about 2 months ago
JSON representation

Module-nomodule implementation that has grown to more than just a POC

• Host: GitHub
• URL: https://github.com/JoviDeCroock/POC-ModularLegacyBuild
• Owner: JoviDeCroock
• Created: 2019-01-18T20:17:44.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2022-12-10T16:55:28.000Z (almost 2 years ago)
• Last Synced: 2024-07-18T10:02:46.963Z (2 months ago)
• Language: JavaScript
• Homepage:
• Size: 1.32 MB
• Stars: 33
• Watchers: 3
• Forks: 3
• Open Issues: 20
• Metadata Files:
  • Readme: readme.md

Awesome Lists containing this project

README

        
# Module builds

This proof of concept shows us:

1. the power of a module build vs a legacy one (smaller and faster)

2. the endless possibilities of this approach

One thing that would need to evolve in the community for this approach to work is to

get rid off the notion that library authors should decide what the minimum down transpiled

code is for their distribution.

This allows developers to choose their crowd and transpile down how much they want to.

To see this code in action:

1. `yarn build`

2. `cd dist && http-server -o`

3. open in chrome, look at network tab

4. open in IE/Safari and look at network tab.

```

Evergreen

main: 2.38KiB

vendors: 48KiB

Nevergreen

main: 2.85KiB

vendors: 78KiB

fetch-polyfill: 8.7KiB

```

Total legacy: 89.55KiB

Total vendors: 50.40KiB