Polyfills split legacy and modern browsers

[rickvandermey]

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request

Command (mark with an x)

- [x] new

Desired functionality

When creating an Angular App with the NG command, i would love to see a split between polyfills for modern browsers and legacy browsers. While building the application the legacy browsers should read all scripts and modern browsers should skip the legacy bundle because of the nomodule attr in scripts.

<script nomodule src="/polyfills-legacy.js"></script>
<script src="/polyfills.js"></script>

For optimization the angular application, this would improve low-end devices with modern browsers. this would be a 35kb vs 13.5kb gzipped difference for modern browsers

[alan-agius4]

This has been implemented and already available in the current beta version.

See: #13403

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}